US: NTCIP Roadside Unit - SNMPv3/TLS
Description
This solution is used within the U.S.. It combines standards associated with US: NTCIP Roadside Unit with those for I–F: SNMPv3/TLS. The US: NTCIP Roadside Unit standards include upper–layer standards required to implement center–to–field roadside unit communications. The I–F: SNMPv3/TLS standards include lower–layer standards that support secure center–to–field and field–to–field communications using simple network management protocol (SNMPv3); implementations are strongly encouraged to use the TLS for SNMP security option for this solution to ensure adequate security.
Includes Standards
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 1218 | National Transportation Communications for ITS Protocol – Object Definitions for Roadside Units (RSUs) | This standard defines SNMP objects (data elements) for monitoring and efficiently controlling roadside units. |
---|
Facilities | NTCIP 1218 | National Transportation Communications for ITS Protocol – Object Definitions for Roadside Units (RSUs) | This standard defines SNMP objects (data elements) for monitoring and efficiently controlling roadside units. |
---|
Readiness: High–Moderate
Readiness Description
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.
Issues
Issue | Severity | Description | Associated Standard | Associated Triple |
---|
Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | TRIMARC (KYTC)=>equipment control commands=>ODOT / KYTC Connected Vehicle Roadside Equipment |
---|
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 Dispatch Facilities=>equipment control commands=>City and County Connected Vehicle Roadside Equipment |
---|
Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | KYTC Traffic Signal Control System=>equipment control commands=>CVG Airport Connected Vehicle Roadside Equipment |
---|
Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | KYTC Traffic Signal Control System=>equipment control commands=>ODOT / KYTC Connected Vehicle Roadside Equipment |
---|
Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | INDOT Traffic Signal Control System=>equipment control commands=>INDOT Connected Vehicle RSE |
---|
Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | ODOT ATMS=>equipment control commands=>INDOT Connected Vehicle RSE |
---|
Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | ODOT ATMS=>equipment control commands=>ODOT / KYTC Connected Vehicle Roadside Equipment |
---|
Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | ODOT Traffic Signal Control System=>equipment control commands=>ODOT / KYTC Connected Vehicle Roadside Equipment |
---|
Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City and County Traffic Control Center=>equipment control commands=>City and County Connected Vehicle Roadside Equipment |
---|
Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City and County Maintenance Operations=>equipment control commands=>City and County Connected Vehicle Roadside Equipment |
---|
Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Cincinnati Public Services Department=>equipment control commands=>City and County Connected Vehicle Roadside Equipment |
---|
Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Hamilton County Maintenance Division=>equipment control commands=>City and County Connected Vehicle Roadside Equipment |
---|
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) |
---|
Still under development | Medium | A draft of the standard has been developed by the working group, but it was still under development at the time this analysis was performed. | NTCIP RSUs | (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) |
---|
Supports Interfaces
Source | Destination | Flow |
---|
Cincinnati Public Services Department | City and County Connected Vehicle Roadside Equipment | equipment control commands |
---|
City and County Connected Vehicle Roadside Equipment | City and County CV Service Monitoring Systems | RSE status |
---|
City and County Maintenance Operations | City and County Connected Vehicle Roadside Equipment | equipment control commands |
---|
City and County Traffic Control Center | City and County Connected Vehicle Roadside Equipment | equipment control commands |
---|
CVG Airport Connected Vehicle Roadside Equipment | CVG Airport CV Service Monitoring Systems | RSE status |
---|
Hamilton County Maintenance Division | City and County Connected Vehicle Roadside Equipment | equipment control commands |
---|
INDOT Connected Vehicle RSE | INDOT CV Service Monitor System | RSE status |
---|
INDOT Traffic Signal Control System | INDOT Connected Vehicle RSE | equipment control commands |
---|
KYTC Traffic Signal Control System | CVG Airport Connected Vehicle Roadside Equipment | equipment control commands |
---|
KYTC Traffic Signal Control System | ODOT / KYTC Connected Vehicle Roadside Equipment | equipment control commands |
---|
ODOT / KYTC Connected Vehicle Roadside Equipment | KYTC CV Service Monitor System | RSE status |
---|
ODOT / KYTC Connected Vehicle Roadside Equipment | ODOT CV Service Monitor System | RSE status |
---|
ODOT ATMS | INDOT Connected Vehicle RSE | equipment control commands |
---|
ODOT ATMS | ODOT / KYTC Connected Vehicle Roadside Equipment | equipment control commands |
---|
ODOT Traffic Signal Control System | ODOT / KYTC Connected Vehicle Roadside Equipment | equipment control commands |
---|
Other City and County Maintenance Dispatch Facilities | City and County Connected Vehicle Roadside Equipment | equipment control commands |
---|
TRIMARC (KYTC) | ODOT / KYTC Connected Vehicle Roadside Equipment | equipment control commands |
---|