OID reference
1.3.6.1.4.1.1206.4.2.17.1.17
<Definition> This object is the unique identifier of the agency for the SPaT and MAP message. This object shall be either a valid OBJECT IDENTIFIER or a null string. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.1.17 <Object Type> P
Identification
{1 3 6 1 4 1 1206 4 2 17 1 17}
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.17.1.17.0
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.
The displayed source records contain one distinct definition. Compare its source records.
spatRoadAuthorityID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
ACCESS read-write
STATUS mandatory
DESCRIPTION "<Definition> This object is the unique identifier of the
agency for the SPaT and MAP message. This object shall be either
a valid OBJECT IDENTIFIER or a null string.
<Object Identifier> 1.3.6.1.4.1.1206.4.2.17.1.17
<Object Type> P"
REFERENCE "SAE J2735 DE_RelativeRoadAuthorityID"
::= { spat 17 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
<Definition> This object is the unique identifier of the agency for the SPaT and MAP message. This object shall be either a valid OBJECT IDENTIFIER or a null string. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.1.17 <Object Type> P
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: spatRoadAuthorityID
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"spatRoadAuthorityID",
"OBJECT-TYPE",
"SYNTAX",
"OBJECT",
"IDENTIFIER",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> This object is the unique identifier of the agency for the SPaT and MAP message. This object shall be either a valid OBJECT IDENTIFIER or a null string. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.1.17 <Object Type> P\"",
"REFERENCE",
"\"SAE J2735 DE_RelativeRoadAuthorityID\"",
"::=",
"{",
"spat",
"17",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OBJECT IDENTIFIER",
null
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> This object is the unique identifier of the agency for the SPaT and MAP message. This object shall be either a valid OBJECT IDENTIFIER or a null string. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.1.17 <Object Type> P"
],
[
"REFERENCE",
"SAE J2735 DE_RelativeRoadAuthorityID"
],
null,
null,
null
]
}Module: NTCIP1217-v01
See published definition above
{'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:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1206.4.2.17.1.1 | spatStatus | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.1.2 | maxAdvisorySpeeds | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.1.3 | advisorySpeedTable | 1 | 7 | |
| 1.3.6.1.4.1.1206.4.2.17.1.4 | maxMovementManeuvers | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.1.5 | movementManeuverTable | 1 | 12 | |
| 1.3.6.1.4.1.1206.4.2.17.1.6 | spatEnabledLanesStatus | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.1.7 | signalStatusTable | 1 | 7 | |
| 1.3.6.1.4.1.1206.4.2.17.1.8 | signalStatusBlock | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.1.9 | movementManeuverStatusBlock | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.1.10 | spatStatus2 | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.1.11 | maxMovementEvents | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.1.12 | signalStatusTable2 | 1 | 9 | |
| 1.3.6.1.4.1.1206.4.2.17.1.13 | maxAdvisorySpeeds2 | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.1.14 | advisorySpeedTable2 | 1 | 7 | |
| 1.3.6.1.4.1.1206.4.2.17.1.15 | maxMovementManeuvers2 | 0 | 0 | |
| 1.3.6.1.4.1.1206.4.2.17.1.16 | movementManeuverTable2 | 1 | 8 | |
| 1.3.6.1.4.1.1206.4.2.17.1.18 | signalStatusBlock2 | 0 | 0 |