This solution is used within the U.S.. It combines standards associated with US: NTCIP Traffic Signal with those for I–F: SNMPv3/TLS. The US: NTCIP Traffic Signal standards include upper–layer standards required to implement center–to–field traffic signal 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.
| 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. |
|---|
| Mgmt | IETF RFC 3411 | An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks | This standard (RFC) defines the basic architecture for SNMPv3 and includes the definition of information objects for managing the SNMP entity's architecture. |
|---|
| Mgmt | IETF RFC 3412 | Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) | This standard (RFC) contains a MIB that assists in managing the message processing and dispatching subsystem of an SNMP entity. |
|---|
| Mgmt | IETF RFC 3413 | Simple Network Management Protocol (SNMP) Applications | This standard (RFC) includes MIBs that allow for the configuration and management of remote Targets, Notifications, and Proxys. |
|---|
| Mgmt | IETF RFC 3414 | User–based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) | This standard (RFC) contains a MIB that assists in configuring and managing the user–based security model. |
|---|
| Mgmt | IETF RFC 3415 | View–based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) | This standard (RFC) contains a MIB that supports the configuration and management of the View–based access control model of SNMP. |
|---|
| Mgmt | IETF RFC 3416 | Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP) | This standard (RFC) defines the message structure and protocol operations used by SNMPv3. |
|---|
| Mgmt | IETF RFC 3418 | Management Information Base (MIB) for the Simple Network Management Protocol (SNMP) | This standard (RFC) defines the MIB to configure and manage an SNMP entity. |
|---|
| Mgmt | IETF RFC 4293 | Management Information Base for the Internet Protocol (IP) | This standard (RFC) defines the MIB that manages an IP entity. |
|---|
| 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 1202 | NTCIP Object Definitions for ASC | This standard defines SNMP objects (data elements) for a center to control a traffic signal and its interface with connected vehicles. |
|---|
| Facilities | NTCIP 1202 | NTCIP Object Definitions for ASC | This standard defines SNMP objects (data elements) for a center to control a traffic signal and its interface with connected vehicles. |
|---|
| Facilities | IETF RFC 3411 | An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks | This standard (RFC) defines the basic architecture for SNMPv3 and includes the definition of information objects for managing the SNMP entity's architecture. |
|---|
| Facilities | IETF RFC 3412 | Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) | This standard (RFC) contains a MIB that assists in managing the message processing and dispatching subsystem of an SNMP entity. |
|---|
| Facilities | IETF RFC 3413 | Simple Network Management Protocol (SNMP) Applications | This standard (RFC) includes MIBs that allow for the configuration and management of remote Targets, Notifications, and Proxys. |
|---|
| Facilities | IETF RFC 3414 | User–based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) | This standard (RFC) contains a MIB that assists in configuring and managing the user–based security model. |
|---|
| Facilities | IETF RFC 3415 | View–based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) | This standard (RFC) contains a MIB that supports the configuration and management of the View–based access control model of SNMP. |
|---|
| Facilities | IETF RFC 3416 | Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP) | This standard (RFC) defines the message structure and protocol operations used by SNMPv3. |
|---|
| TransNet | IETF RFC 2460 | Internet Protocol, Version 6 (IPv6) Specification | This standard (RFC) specifies version 6 of the Internet Protocol (IPv6), also sometimes referred to as IP Next Generation or IPng. |
|---|
| TransNet | IETF RFC 4291 | IP Version 6 Addressing Architecture | This standard (RFC) defines the addressing architecture of the IP Version 6 (IPv6) protocol. It includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses. |
|---|
| TransNet | IETF RFC 4443 | Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification | This standard (RFC) defines the control messages to manage IPv6. |
|---|
| TransNet | IETF RFC 793 | Transmission Control Protocol | This standard (RFC) defines the main connection–oriented Transport Layer protocol used on Internet–based networks. |
|---|
| Access | NTCIP 2104 | NTCIP SP–Ethernet | This standard defines the Access Layer for center–to–field communications where the local connection is some variant of Ethernet. |
|---|
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 |
|---|
| Data not defined (high) | High | Required data elements are not defined. | (None) | City of Toledo ITS Field Devices=>mixed use crossing status=>ODOT Connected Vehicles Roadside Equipment |
|---|
| Data not defined (high) | High | Required data elements are not defined. | (None) | ODOT District 2 Traffic Signal Roadway Equipment=>mixed use crossing status=>ODOT Connected Vehicles Roadside Equipment |
|---|
| Data not defined (high) | High | Required data elements are not defined. | (None) | City of Bowling Green ITS Field Devices=>mixed use crossing status=>County and City Connected Vehicles Roadside Equipment |
|---|
| Data not defined (high) | High | Required data elements are not defined. | (None) | Lucas County ITS Field Devices=>mixed use crossing status=>County and City Connected Vehicles Roadside Equipment |
|---|
| Data not defined (high) | High | Required data elements are not defined. | (None) | Municipal ITS Field Devices=>mixed use crossing status=>County and City Connected Vehicles Roadside Equipment |
|---|
| Data not defined (high) | High | Required data elements are not defined. | (None) | City of Toledo ITS Field Devices=>mixed use crossing status=>County and City Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Toledo Traffic Management System=>mixed use safety warning control=>City of Toledo ITS Field Devices |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Municipal ITS Field Devices=>intersection control status=>County and City Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Municipal ITS Field Devices=>mixed use crossing status=>County and City Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Municipal ITS Field Devices=>mixed use safety warning status=>Municipal Traffic Signal Systems |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Toledo ITS Field Devices=>intersection control status=>County and City Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Toledo ITS Field Devices=>mixed use crossing status=>County and City Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Bowling Green Traffic Signal System=>mixed use safety warning control=>City of Bowling Green ITS Field Devices |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Toledo ITS Field Devices=>mixed use crossing status=>ODOT Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Municipal Traffic Signal Systems=>mixed use safety warning control=>Municipal ITS Field Devices |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Toledo ITS Field Devices=>mixed use safety warning status=>City of Toledo Traffic Management System |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Toledo ITS Field Devices=>intersection control status=>ODOT Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Lucas County ITS Field Devices=>mixed use safety warning status=>Lucas County Traffic Signal System |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Lucas County ITS Field Devices=>mixed use crossing status=>County and City Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Lucas County Traffic Signal System=>mixed use safety warning control=>Lucas County ITS Field Devices |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Bowling Green ITS Field Devices=>mixed use safety warning status=>City of Bowling Green Traffic Signal System |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Bowling Green ITS Field Devices=>mixed use crossing status=>County and City Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Bowling Green ITS Field Devices=>intersection control status=>County and City Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | ODOT District 2 Traffic Signal Roadway Equipment=>mixed use crossing status=>ODOT Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | ODOT District 2 Traffic Signal Roadway Equipment=>intersection control status=>ODOT Connected Vehicles Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Lucas County ITS Field Devices=>intersection control status=>County and City Connected Vehicles 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) |
|---|
| 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) |
|---|
| Source | Destination | Flow |
|---|
| City of Bowling Green ITS Field Devices | City of Bowling Green Traffic Signal System | mixed use safety warning status |
|---|
| City of Bowling Green ITS Field Devices | City of Bowling Green Traffic Signal System | signal control status |
|---|
| City of Bowling Green ITS Field Devices | County and City Connected Vehicles Roadside Equipment | conflict monitor status |
|---|
| City of Bowling Green ITS Field Devices | County and City Connected Vehicles Roadside Equipment | intersection control status |
|---|
| City of Bowling Green ITS Field Devices | County and City Connected Vehicles Roadside Equipment | mixed use crossing status |
|---|
| City of Bowling Green Traffic Signal System | City of Bowling Green ITS Field Devices | mixed use safety warning control |
|---|
| City of Bowling Green Traffic Signal System | County and City Connected Vehicles Roadside Equipment | intersection management application info |
|---|
| City of Toledo ITS Field Devices | City of Toledo Traffic Management System | mixed use safety warning status |
|---|
| City of Toledo ITS Field Devices | City of Toledo Traffic Management System | signal control status |
|---|
| City of Toledo ITS Field Devices | County and City Connected Vehicles Roadside Equipment | conflict monitor status |
|---|
| City of Toledo ITS Field Devices | County and City Connected Vehicles Roadside Equipment | intersection control status |
|---|
| City of Toledo ITS Field Devices | County and City Connected Vehicles Roadside Equipment | mixed use crossing status |
|---|
| City of Toledo ITS Field Devices | ODOT Connected Vehicles Roadside Equipment | intersection control status |
|---|
| City of Toledo ITS Field Devices | ODOT Connected Vehicles Roadside Equipment | mixed use crossing status |
|---|
| City of Toledo Traffic Management System | City of Toledo ITS Field Devices | mixed use safety warning control |
|---|
| City of Toledo Traffic Management System | County and City Connected Vehicles Roadside Equipment | intersection management application info |
|---|
| Lucas County ITS Field Devices | County and City Connected Vehicles Roadside Equipment | conflict monitor status |
|---|
| Lucas County ITS Field Devices | County and City Connected Vehicles Roadside Equipment | intersection control status |
|---|
| Lucas County ITS Field Devices | County and City Connected Vehicles Roadside Equipment | mixed use crossing status |
|---|
| Lucas County ITS Field Devices | Lucas County Traffic Signal System | mixed use safety warning status |
|---|
| Lucas County ITS Field Devices | Lucas County Traffic Signal System | signal control status |
|---|
| Lucas County ITS Field Devices | ODOT District 2 Office | signal control status |
|---|
| Lucas County ITS Field Devices | ODOT Traffic Signal Control System | signal control status |
|---|
| Lucas County Traffic Signal System | County and City Connected Vehicles Roadside Equipment | intersection management application info |
|---|
| Lucas County Traffic Signal System | Lucas County ITS Field Devices | mixed use safety warning control |
|---|
| Monroe County ITS Field Equipment | Monroe County Road Commission Traffic Operations Center | signal control status |
|---|
| Municipal ITS Field Devices | County and City Connected Vehicles Roadside Equipment | conflict monitor status |
|---|
| Municipal ITS Field Devices | County and City Connected Vehicles Roadside Equipment | intersection control status |
|---|
| Municipal ITS Field Devices | County and City Connected Vehicles Roadside Equipment | mixed use crossing status |
|---|
| Municipal ITS Field Devices | Municipal Traffic Signal Systems | mixed use safety warning status |
|---|
| Municipal ITS Field Devices | Municipal Traffic Signal Systems | signal control status |
|---|
| Municipal Traffic Signal Systems | County and City Connected Vehicles Roadside Equipment | intersection management application info |
|---|
| Municipal Traffic Signal Systems | Municipal ITS Field Devices | mixed use safety warning control |
|---|
| ODOT ATMS | ODOT Connected Vehicles Roadside Equipment | intersection management application info |
|---|
| ODOT District 2 Traffic Signal Roadway Equipment | ODOT Connected Vehicles Roadside Equipment | conflict monitor status |
|---|
| ODOT District 2 Traffic Signal Roadway Equipment | ODOT Connected Vehicles Roadside Equipment | intersection control status |
|---|
| ODOT District 2 Traffic Signal Roadway Equipment | ODOT Connected Vehicles Roadside Equipment | mixed use crossing status |
|---|
| ODOT District 2 Traffic Signal Roadway Equipment | ODOT District 2 Office | signal control status |
|---|
| ODOT District 2 Traffic Signal Roadway Equipment | ODOT Traffic Signal Control System | signal control status |
|---|
| ODOT Traffic Signal Control System | ODOT Connected Vehicles Roadside Equipment | intersection management application info |
|---|