OID reference

mapLaneAttribute

1.3.6.1.4.1.1206.4.2.17.2.4.1.8

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.2.17.2.4.1 (mapLaneEntry)
Node code: 8
Node name: mapLaneAttribute
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.2.17.2.4.1.8
URN notation: urn:oid:1.3.6.1.4.1.1206.4.2.17.2.4.1.8

ASN.1, OID-IRI and named path variants

ASN.1 notation

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

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) saeNtcip(17) map(2) mapLaneTable(4) mapLaneEntry(1) mapLaneAttribute(8)}

OID-IRI notation

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

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/org/dod/internet/private/enterprise/1206/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/org/dod/internet/private/enterprise/nema/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/org/dod/internet/private/enterprises/1206/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/org/dod/internet/private/enterprises/nema/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
/iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/saeNtcip/map/mapLaneTable/mapLaneEntry/mapLaneAttribute
Additional combinations skipped.

SNMP properties

Value type: INTEGER
Maximum access defined by MIB: read-write
Status in MIB: deprecated

Allowed ranges: 0–65535

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 NTCIP1217-v01, the row index mapLaneIndex 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.17.2.4.1.8.<mapLaneIndex>. 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.17.2.4.1.8

Replace the placeholders with your connection and authentication options. Some definitions do not specify a readable access value. 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

mapLaneAttribute · unspecified

mapLaneAttribute   OBJECT-TYPE
      DESCRIPTION "<Definition> For NTCIP 1202 user clarification, if a
            specific attribute for the lane is true, the associated bit shall
            be set to (1). Bit 0 is equal to Bit 0 of the BIT STRING of the
            appropriate LaneAttribute type, Bit 1 is equal to Bit 1, etc. If
            the mapLaneType is vehicle (0), then the attribute values are
            defined by SAE J2735_201603 DE_LaneAttributes-Vehicle.
      If the mapLaneType is crosswalk (1), then the attribute values are
            defined by SAE J2735_201603 DE_LaneAttributes-Crosswalk.
      If the mapLaneType is bikelane (2), then the attribute values are
            defined by SAE J2735_201603 DE_LaneAttributes-Bike.
      If the mapLaneType is sidewalk (3), then the attribute values are
            defined by SAE J2735_201603 DE_LaneAttributes-Sidewalk.
      If the mapLaneType is median (4), then the attribute values are defined
            by SAE J2735_201603 DE_LaneAttributes-Barrier.



                                                                                        

                  
        

      If the mapLaneType is striping (5), then the attribute values are
            defined by SAE J2735_201603 DE_LaneAttributes-Striping.
      If the mapLaneType is trackedvehicle(6), then the attribute values are
            defined by SAE J2735_201603 DE_LaneAttributes-TrackedVehicle.
      If the mapLaneType is parking (7), then the attribute values are
            defined by SAE J2735_201603 DE_LaneAttributes-ParkingLane.
      Note: Bit 0 should not be enabled as a revocable lane for mapLaneIndex
            = 255. It is reserved for spatEnabledLanesCommand.
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.4.1.8"
      REFERENCE "SAE J2735_201603 DF_LaneTypeAttributes"
::= { mapLaneEntry 8 }

mapLaneAttribute · deprecated

mapLaneAttribute    OBJECT-TYPE
      SYNTAX    INTEGER (0..65535)
      ACCESS read-write
      STATUS deprecated
      DESCRIPTION "<Definition> For NTCIP 1202 user clarification, if a
             specific attribute for the lane is true, the associated bit shall
             be set to (1). Bit 0 is equal to Bit 0 of the BIT STRING of the
             appropriate LaneAttribute type, Bit 1 is equal to Bit 1, etc. If
             the mapLaneType is vehicle (0), then the attribute values are
             defined by SAE J2735 DE_LaneAttributes-Vehicle.
      If the mapLaneType is crosswalk (1), then the attribute values are
             defined by SAE J2735 DE_LaneAttributes-Crosswalk.



                                                                                    

                                                                                   
                                                                                  

      If the mapLaneType is bikelane (2), then the attribute values are
            defined by SAE J2735 DE_LaneAttributes-Bike.
      If the mapLaneType is sidewalk (3), then the attribute values are
            defined by SAE J2735 DE_LaneAttributes-Sidewalk.
      If the mapLaneType is median (4), then the attribute values are defined
            by SAE J2735 DE_LaneAttributes-Barrier.
      If the mapLaneType is striping (5), then the attribute values are
            defined by SAE J2735 DE_LaneAttributes-Striping.
      If the mapLaneType is trackedvehicle(6), then the attribute values are
            defined by SAE J2735 DE_LaneAttributes-TrackedVehicle.
      If the mapLaneType is parking (7), then the attribute values are
            defined by SAE J2735 DE_LaneAttributes-ParkingLane.
      Note: Bit 0 should not be enabled as a revocable lane for mapLaneIndex
            = 255. It is reserved for spatEnabledLanesCommand.
      <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.4.1.8"
      REFERENCE "SAE J2735 DF_LaneTypeAttributes"
::= { mapLaneEntry 8 }

Meaning

Descriptions

2 unique

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

Description 1

<Definition> For NTCIP 1202 user clarification, if a specific attribute for the lane is true, the associated bit shall be set to (1). Bit 0 is equal to Bit 0 of the BIT STRING of the appropriate LaneAttribute type, Bit 1 is equal to Bit 1, etc. If the mapLaneType is vehicle (0), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Vehicle. If the mapLaneType is crosswalk (1), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Crosswalk. If the mapLaneType is bikelane (2), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Bike. If the mapLaneType is sidewalk (3), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Sidewalk. If the mapLaneType is median (4), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Barrier. If the mapLaneType is striping (5), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Striping. If the mapLaneType is trackedvehicle(6), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-TrackedVehicle. If the mapLaneType is parking (7), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-ParkingLane. Note: Bit 0 should not be enabled as a revocable lane for mapLaneIndex = 255. It is reserved for spatEnabledLanesCommand. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.4.1.8

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 1 matching source record

Description 2

<Definition> For NTCIP 1202 user clarification, if a specific attribute for the lane is true, the associated bit shall be set to (1). Bit 0 is equal to Bit 0 of the BIT STRING of the appropriate LaneAttribute type, Bit 1 is equal to Bit 1, etc. If the mapLaneType is vehicle (0), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Vehicle. If the mapLaneType is crosswalk (1), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Crosswalk. If the mapLaneType is bikelane (2), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Bike. If the mapLaneType is sidewalk (3), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Sidewalk. If the mapLaneType is median (4), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Barrier. If the mapLaneType is striping (5), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Striping. If the mapLaneType is trackedvehicle(6), then the attribute values are defined by SAE J2735 DE_LaneAttributes-TrackedVehicle. If the mapLaneType is parking (7), then the attribute values are defined by SAE J2735 DE_LaneAttributes-ParkingLane. Note: Bit 0 should not be enabled as a revocable lane for mapLaneIndex = 255. It is reserved for spatEnabledLanesCommand. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.4.1.8

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

mapLaneAttribute · unspecifiedNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: unspecified.

Names: mapLaneAttribute

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "mapLaneAttribute",
    "OBJECT-TYPE",
    "DESCRIPTION",
    "\"<Definition> For NTCIP 1202 user clarification, if a specific attribute for the lane is true, the associated bit shall be set to (1). Bit 0 is equal to Bit 0 of the BIT STRING of the appropriate LaneAttribute type, Bit 1 is equal to Bit 1, etc. If the mapLaneType is vehicle (0), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Vehicle. If the mapLaneType is crosswalk (1), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Crosswalk. If the mapLaneType is bikelane (2), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Bike. If the mapLaneType is sidewalk (3), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Sidewalk. If the mapLaneType is median (4), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Barrier. If the mapLaneType is striping (5), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-Striping. If the mapLaneType is trackedvehicle(6), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-TrackedVehicle. If the mapLaneType is parking (7), then the attribute values are defined by SAE J2735_201603 DE_LaneAttributes-ParkingLane. Note: Bit 0 should not be enabled as a revocable lane for mapLaneIndex = 255. It is reserved for spatEnabledLanesCommand. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.4.1.8\"",
    "REFERENCE",
    "\"SAE J2735_201603 DF_LaneTypeAttributes\"",
    "::=",
    "{",
    "mapLaneEntry",
    "8",
    "}"
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1202 v03A, Object Definitions for Actuated Signal Controllers (ASC) Interface Published May 2019 — original PDF · Official record
Module: NTCIP1217-v01

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['Devices', 'OerString'], 'NTCIP1202-v03': ['channelNumber']}
```
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. The declaration also has invalid SMI syntax; its type constraints were not validated.
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: missing or unreadable imports of devices. 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 NTCIP-1202v0328A.pdf — NTCIP1217-v01 (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

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

Status in source: deprecated.

Names: mapLaneAttribute

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "mapLaneAttribute",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "(",
    "0",
    ".",
    ".",
    "65535",
    ")",
    "ACCESS",
    "read-write",
    "STATUS",
    "deprecated",
    "DESCRIPTION",
    "\"<Definition> For NTCIP 1202 user clarification, if a specific attribute for the lane is true, the associated bit shall be set to (1). Bit 0 is equal to Bit 0 of the BIT STRING of the appropriate LaneAttribute type, Bit 1 is equal to Bit 1, etc. If the mapLaneType is vehicle (0), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Vehicle. If the mapLaneType is crosswalk (1), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Crosswalk. If the mapLaneType is bikelane (2), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Bike. If the mapLaneType is sidewalk (3), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Sidewalk. If the mapLaneType is median (4), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Barrier. If the mapLaneType is striping (5), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Striping. If the mapLaneType is trackedvehicle(6), then the attribute values are defined by SAE J2735 DE_LaneAttributes-TrackedVehicle. If the mapLaneType is parking (7), then the attribute values are defined by SAE J2735 DE_LaneAttributes-ParkingLane. Note: Bit 0 should not be enabled as a revocable lane for mapLaneIndex = 255. It is reserved for spatEnabledLanesCommand. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.4.1.8\"",
    "REFERENCE",
    "\"SAE J2735 DF_LaneTypeAttributes\"",
    "::=",
    "{",
    "mapLaneEntry",
    "8",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "integerSubType",
        [
          [
            0,
            65535
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "deprecated"
    ],
    [
      "DESCRIPTION",
      "<Definition> For NTCIP 1202 user clarification, if a specific attribute for the lane is true, the associated bit shall be set to (1). Bit 0 is equal to Bit 0 of the BIT STRING of the appropriate LaneAttribute type, Bit 1 is equal to Bit 1, etc. If the mapLaneType is vehicle (0), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Vehicle. If the mapLaneType is crosswalk (1), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Crosswalk. If the mapLaneType is bikelane (2), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Bike. If the mapLaneType is sidewalk (3), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Sidewalk. If the mapLaneType is median (4), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Barrier. If the mapLaneType is striping (5), then the attribute values are defined by SAE J2735 DE_LaneAttributes-Striping. If the mapLaneType is trackedvehicle(6), then the attribute values are defined by SAE J2735 DE_LaneAttributes-TrackedVehicle. If the mapLaneType is parking (7), then the attribute values are defined by SAE J2735 DE_LaneAttributes-ParkingLane. Note: Bit 0 should not be enabled as a revocable lane for mapLaneIndex = 255. It is reserved for spatEnabledLanesCommand. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.2.4.1.8"
    ],
    [
      "REFERENCE",
      "SAE J2735 DF_LaneTypeAttributes"
    ],
    null,
    null,
    null
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1202 v03b NTCIP 1202 v02, Object Definitions for Actuated Traffic Signal Controller (ASC) Units – version 03b Published October 2023 — original PDF · Official record
Module: NTCIP1217-v01

See published definition above
Module imports
```
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1213-MIB': ['DisplayString', 'ifIndex'], 'NTCIP8004v02': ['devices', 'OerString'], 'NTCIP1202-v03': ['channelNumber', 'signalGroupEntryNumber']}
```
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: The mapSpeedLimitType DESCRIPTION starts with a duplicated malformed prefix. Mask only the extra DESCRIPTION prefix in an equal-length parsing copy, retaining the complete following native DESCRIPTION, original definition and unchanged OID assignment.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004v02. 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 NTCIP-1202v03.35e-aspublished.pdf — NTCIP1217-v01 (MIB transcription)
Related source files and packages:
- NTCIP 1202 v03b NTCIP 1202 v02, Object Definitions for Actuated Traffic Signal Controller (ASC) Units – version 03b Published October 2023 — original PDF

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (12)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.1206.4.2.17.2.4.1.1	mapLaneIndex	0	0
1.3.6.1.4.1.1206.4.2.17.2.4.1.2	mapLaneIntersection	0	0
1.3.6.1.4.1.1206.4.2.17.2.4.1.3	mapLaneNumber	0	0
1.3.6.1.4.1.1206.4.2.17.2.4.1.4	mapLaneName	0	0
1.3.6.1.4.1.1206.4.2.17.2.4.1.5	mapLaneDirection	0	0
1.3.6.1.4.1.1206.4.2.17.2.4.1.6	mapLaneSharing	0	0
1.3.6.1.4.1.1206.4.2.17.2.4.1.7	mapLaneType	0	0
1.3.6.1.4.1.1206.4.2.17.2.4.1.9	mapLaneManeuver	0	0
1.3.6.1.4.1.1206.4.2.17.2.4.1.10	mapLaneOverlay	0	0
1.3.6.1.4.1.1206.4.2.17.2.4.1.11	mapLaneIngress	0	0
1.3.6.1.4.1.1206.4.2.17.2.4.1.12	mapLaneEgress	0	0
1.3.6.1.4.1.1206.4.2.17.2.4.1.13	mapLaneCRC	0	0