This solution is used within the U.S.. It combines standards associated with US: NTCIP Warning Device with those for I–M: Wireless SNMPv3/TLS. The US: NTCIP Warning Device standards include a composite of upper–layer standards that support monitoring for unsafe traffic activities and displaying warning to drivers. The I–M: Wireless SNMPv3/TLS standards include lower–layer standards that support secure infrastructure–to–mobile communications using simple network management protocol (SNMPv3).
| Level | DocNum | FullName | Description |
|---|
| Mgmt | NTCIP 1201 | NTCIP Global Object (GO) Definitions | This standard defines SNMP objects (data elements) used by a wide range of field devices like time and versioning information. |
|---|
| Security | IETF RFC 6353 | Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP) | This standard (RFC) defines how to use the TLS authentication service to provide authentication within the access control mechanism of SNMP. |
|---|
| ITS Application Entity | NTCIP 1209 | NTCIP Object Definitions for Transportation Sensor Systems (TSS) | This standard defines SNMP objects (data elements) to monitor and control transportation system sensors that measure real–time vehicular traffic information. |
|---|
| ITS Application Entity | NTCIP 1205 | NTCIP Objects for CCTV Camera Control | This standard defines SNMP objects (data elements) for control and monitoring of closed–circuit television (CCTV) camera controllers. |
|---|
| ITS Application Entity | NTCIP 1203 | NTCIP Object Definitions for Dynamic Message Signs (DMS) | This standard defines SNMP objects (data elements) for monitoring and controlling dynamic message signs (such as variable message signs). |
|---|
| Facilities | NTCIP 1209 | NTCIP Object Definitions for Transportation Sensor Systems (TSS) | This standard defines SNMP objects (data elements) to monitor and control transportation system sensors that measure real–time vehicular traffic information. |
|---|
| Facilities | NTCIP 1205 | NTCIP Objects for CCTV Camera Control | This standard defines SNMP objects (data elements) for control and monitoring of closed–circuit television (CCTV) camera controllers. |
|---|
| Facilities | NTCIP 1203 | NTCIP Object Definitions for Dynamic Message Signs (DMS) | This standard defines SNMP objects (data elements) for monitoring and controlling dynamic message signs (such as variable message signs). |
|---|
One significant or possibly a couple minor issues. For existing deployments, the chosen solution likely has identified security or management issues not addressed by the communications solution. Deployers should consider additional security measures, such as communications link and physical security as part of these solutions. They should also review the management issues to see if they are relevant to their deployment and would require mitigation. For new deployments, the deployment efforts should consider a path to addressing these issues as a part of their design activities. The solution does not by itself provide a fully secure implementation without additional work.
| Issue | Severity | Description | Associated Standard | Associated Triple |
|---|
| Use case not considered in design (critical) | High | While the indicated standards nominally address the information flow, the design details may not meet performance or other requirements because this particular use case was not the focus of the design effort. | (None) | Hamilton County Maintenance Vehicle=>work zone warning status=>Hamilton County Maintenance Division |
|---|
| Use case not considered in design (critical) | High | While the indicated standards nominally address the information flow, the design details may not meet performance or other requirements because this particular use case was not the focus of the design effort. | (None) | KYTC District 6 Maintenance Vehicles=>work zone warning status=>KYTC District 6 Maintenance Garages |
|---|
| Use case not considered in design (critical) | High | While the indicated standards nominally address the information flow, the design details may not meet performance or other requirements because this particular use case was not the focus of the design effort. | (None) | Cincinnati Maintenance Vehicles=>work zone warning status=>Cincinnati Public Services Department |
|---|
| Use case not considered in design (critical) | High | While the indicated standards nominally address the information flow, the design details may not meet performance or other requirements because this particular use case was not the focus of the design effort. | (None) | ODOT Maintenance Vehicles=>work zone warning status=>ODOT District 8 Maintenance Garages |
|---|
| Use case not considered in design (critical) | High | While the indicated standards nominally address the information flow, the design details may not meet performance or other requirements because this particular use case was not the focus of the design effort. | (None) | City and County Maintenance Vehicles=>work zone warning status=>Cincinnati Public Services Department |
|---|
| Use case not considered in design (critical) | High | While the indicated standards nominally address the information flow, the design details may not meet performance or other requirements because this particular use case was not the focus of the design effort. | (None) | Other City and County Maintenance Vehicles=>work zone warning status=>Cincinnati Public Services Department |
|---|
| Use case not considered in design (critical) | High | While the indicated standards nominally address the information flow, the design details may not meet performance or other requirements because this particular use case was not the focus of the design effort. | (None) | Other City and County Maintenance Vehicles=>work zone warning status=>Other City and County Maintenance Dispatch Facilities |
|---|
| Use case not considered in design (critical) | High | While the indicated standards nominally address the information flow, the design details may not meet performance or other requirements because this particular use case was not the focus of the design effort. | (None) | INDOT Maintenance Vehicles=>work zone warning status=>INDOT Seymour District Maintenance Garages |
|---|
| Use case not considered in design (critical) | High | While the indicated standards nominally address the information flow, the design details may not meet performance or other requirements because this particular use case was not the focus of the design effort. | (None) | City and County Maintenance Vehicles=>work zone warning status=>Other City and County Maintenance Dispatch Facilities |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Other City and County Maintenance Vehicles=>work zone warning status=>Other City and County Maintenance Dispatch Facilities |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | KYTC District 6 Maintenance Vehicles=>work zone warning status=>KYTC District 6 Maintenance Garages |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Hamilton County Maintenance Vehicle=>work zone warning status=>Hamilton County Maintenance Division |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Cincinnati Maintenance Vehicles=>work zone warning status=>Cincinnati Public Services Department |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | ODOT Maintenance Vehicles=>work zone warning status=>ODOT District 8 Maintenance Garages |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City and County Maintenance Vehicles=>work zone warning status=>Cincinnati Public Services Department |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | INDOT Maintenance Vehicles=>work zone warning status=>INDOT Seymour District Maintenance Garages |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Other City and County Maintenance Vehicles=>work zone warning status=>Cincinnati Public Services Department |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City and County Maintenance Vehicles=>work zone warning status=>Other City and County Maintenance Dispatch Facilities |
|---|
| Out of date (medium) | Medium | The standard includes normative references to other standards that have been subject to significant changes that can impact interoperability or security of systems and the industry has not specified if and how these updates should be implemented for deployments of this standard. | IETF RFC 6353 TLS for SNMP | (All) |
|---|
| Update data to SNMPv3 | Low | Data has been defined for SNMPv1, but needs to be updated to SNMPv3 format. | (None) | (All) |
|---|
| Use TLS for SNMP Option | Low | The standard allows for multiple security mechanisms. The only defined mechanism that meets the requirements for C–ITS is the one based on TLS. | (None) | (All) |
|---|