OID reference

priorityStrategyRequestedTable

1.3.6.1.4.1.1206.4.2.11.3.2

Description

A static table containing the parameters associated with executing a priority strategy. The number of rows in this table is equal to 10.

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1206.4.2.11.3 (priorityStrategyServer)
Node code: 2
Node name: priorityStrategyRequestedTable
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1206.4.2.11.3.2
URN notation: urn:oid:1.3.6.1.4.1.1206.4.2.11.3.2

ASN.1, OID-IRI and named path variants

ASN.1 notation

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

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) scp(11) priorityStrategyServer(3) priorityStrategyRequestedTable(2)}

OID-IRI notation

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

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/org/dod/internet/private/enterprise/1206/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/org/dod/internet/private/enterprise/nema/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/org/dod/internet/private/enterprises/1206/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/org/dod/internet/private/enterprises/nema/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
/iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/scp/priorityStrategyServer/priorityStrategyRequestedTable
Additional combinations skipped.

Published definitions

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

Show 2 published definitions

priorityStrategyRequestedTable · mandatory

priorityStrategyRequestedTable OBJECT-TYPE
       SYNTAX         SEQUENCE OF priorityStrategyRequestedEntry
       ACCESS         not-accessible
       STATUS         mandatory
       DESCRIPTION
              "A static table containing the parameters associated with
              executing a priority strategy. The number of rows in this table
              is equal to 10."
::= { priorityStrategyServer 2 }

priorityStrategyRequestedTable · optional

priorityStrategyRequestedTable   OBJECT-TYPE
      SYNTAX   SEQUENCE OF priorityStrategyRequestedEntry
      ACCESS   not-accessible
      STATUS   optional
      DESCRIPTION
          "A static table containing the parameters associated with executing
          a priority strategy. The number of rows in this table is equal to
          10."
::= { priorityStrategyServer 2 }

Meaning

Descriptions

1 unique

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

A static table containing the parameters associated with executing a priority strategy. The number of rows in this table is equal to 10.

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 2 matching source records

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)2 records · 2 sources

Description 1

priorityStrategyRequestedTable · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: priorityStrategyRequestedTable

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "priorityStrategyRequestedTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "priorityStrategyRequestedEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"A static table containing the parameters associated with executing a priority strategy. The number of rows in this table is equal to 10.\"",
    "::=",
    "{",
    "priorityStrategyServer",
    "2",
    "}"
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1211 v02, Object Definitions for Signal Control and Prioritization (SCP) Published September 2014 — original PDF · Official record
Module: CO-MIB1

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. 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: The DESCRIPTION contains an interior ASCII quotation mark that incorrectly terminates the string before OR'ed. Normalize only the interior opening quote to typographic form in the parser copy, retaining the original definition. No numeric assignment changes.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of scp. 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.
Source data warning: This module uses explicit parent OID expressions with an omitted SMI type: priorityStrategyServer ::= { scp 3 }, priorityStrategyMessages ::= { scp 4}. These assignments are interpreted as OID groupings for the native child objects. The type omission and original expressions remain visible; consult the original PDF before implementation.
Related ASN.1 definitions
```
priorityStrategyServer ::= { scp 3 }
```
```
priorityStrategyMessages ::= { scp 4}
```
· Download NTCIP1211-v0224j.pdf — CO-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

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

Status in source: optional.

Names: priorityStrategyRequestedTable

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "priorityStrategyRequestedTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "priorityStrategyRequestedEntry",
    "ACCESS",
    "not-accessible",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"A static table containing the parameters associated with executing a priority strategy. The number of rows in this table is equal to 10.\"",
    "::=",
    "{",
    "priorityStrategyServer",
    "2",
    "}"
  ]
}

NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1211 v01, Object Definitions for Signal Control and Prioritization Published May 2008 (superceded by NTCIP 1211 v02) — original PDF · Official record
Module: CO-MIB1

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. 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: The DESCRIPTION contains an interior ASCII quotation mark that incorrectly terminates the string before OR'ed. Normalize only the interior opening quote to typographic form in the parser copy, retaining the original definition. No numeric assignment changes.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of scp. 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.
Source data warning: This module uses explicit parent OID expressions with an omitted SMI type: priorityStrategyServer ::= { scp 3 }, priorityStrategyMessages ::= { scp 4}. These assignments are interpreted as OID groupings for the native child objects. The type omission and original expressions remain visible; consult the original PDF before implementation.
Related ASN.1 definitions
```
priorityStrategyServer ::= { scp 3 }
```
```
priorityStrategyMessages ::= { scp 4}
```
· Download 1211v0138p-2008b_Final.pdf — CO-MIB1 (MIB transcription)
Related source files and packages:
- NTCIP 1211 v01, Object Definitions for Signal Control and Prioritization Published May 2008 (superceded by NTCIP 1211 v02) — original PDF

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Direct children (1)

OID	Name	Direct children	Descendants	Description
1.3.6.1.4.1.1206.4.2.11.3.2.1	priorityStrategyRequestedEntry	5	5

Siblings (6)

OID	Name	Direct children	Descendants
1.3.6.1.4.1.1206.4.2.11.3.1	maxStrategyRequestsToConsider	0	0
1.3.6.1.4.1.1206.4.2.11.3.3	coBusy	0	0
1.3.6.1.4.1.1206.4.2.11.3.4	priorityStrategiesMax	0	0
1.3.6.1.4.1.1206.4.2.11.3.5	priorityStrategyTable	1	6
1.3.6.1.4.1.1206.4.2.11.3.6	priorityStrategyExtensionToSplitTable	1	3
1.3.6.1.4.1.1206.4.2.11.3.7	priorityStrategyDefaultCoordPattern	0	0