This solution is used within the U.S.. It combines standards associated with US: NTCIP Warning Device with those for I–F: 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–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 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 | 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. |
|---|
| 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). |
|---|
| 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 |
|---|
| 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) | Wood County ITS Field Devices=>work zone warning status=>Wood County Maintenance Dispatch |
|---|
| 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) | Municipal ITS Field Devices=>work zone warning status=>Municipal Maintenance Dispatch |
|---|
| 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) | Lucas County ITS Field Devices=>work zone warning status=>Lucas County Engineer Dispatch |
|---|
| 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 of Bowling Green ITS Field Devices=>work zone warning status=>City of Bowling Green Maintenance Dispatch |
|---|
| 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 of Bowling Green ITS Field Devices=>work zone warning status=>City of Bowling Green Public Works Dispatch |
|---|
| 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 of Bowling Green ITS Field Devices=>work zone warning status=>City of Bowling Green Electric Division Dispatch |
|---|
| 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 District 2 DMS=>work zone warning status=>ODOT District 2 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) | ODOT District 2 DMS=>lane management information=>ODOT ATMS |
|---|
| 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 District 2 Lane Control Devices=>lane management information=>ODOT ATMS |
|---|
| 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) | MDOT ITS Field Equipment=>lane management information=>MDOT Statewide TMC |
|---|
| 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 of Toledo ITS Field Devices=>work zone warning status=>City of Toledo Maintenance Dispatch (CLIC) |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Municipal ITS Field Devices=>work zone warning status=>Municipal Maintenance Dispatch |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Municipal Maintenance Dispatch=>work zone warning device 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) | Lucas County Engineer Dispatch=>work zone warning device 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) | Lucas County ITS Field Devices=>work zone warning status=>Lucas County Engineer Dispatch |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Wood County ITS Field Devices=>work zone warning status=>Wood County Maintenance Dispatch |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Wood County Maintenance Dispatch=>work zone warning device control=>Wood 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 Maintenance Dispatch=>work zone warning device 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) | ODOT District 2 Maintenance Garages=>speed monitoring control=>ODOT District 2 Speed Monitoring Roadside Equipment |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | ODOT ATMS=>speed monitoring control=>ODOT District 2 Speed Monitoring 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=>work zone warning status=>City of Toledo Maintenance Dispatch (CLIC) |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | ODOT District 2 DMS=>work zone warning status=>ODOT District 2 Maintenance Garages |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | ODOT District 2 Office=>speed monitoring control=>ODOT District 2 Speed Monitoring 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=>work zone warning status=>City of Bowling Green Maintenance Dispatch |
|---|
| 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=>work zone warning status=>City of Bowling Green Public Works Dispatch |
|---|
| 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=>work zone warning status=>City of Bowling Green Electric Division Dispatch |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Toledo Maintenance Dispatch (CLIC)=>work zone warning device 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) | City of Bowling Green Electric Division Dispatch=>work zone warning device 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) | ODOT District 2 Speed Monitoring Roadside Equipment=>speed monitoring information=>ODOT District 2 Maintenance Garages |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | ODOT District 2 Speed Monitoring Roadside Equipment=>speed monitoring information=>ODOT District 2 Office |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | ODOT District 2 Speed Monitoring Roadside Equipment=>speed monitoring information=>ODOT ATMS |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | City of Bowling Green Public Works Dispatch=>work zone warning device control=>City of Bowling Green ITS Field Devices |
|---|
| 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 Electric Division Dispatch | City of Bowling Green ITS Field Devices | work zone warning device control |
|---|
| City of Bowling Green ITS Field Devices | City of Bowling Green Electric Division Dispatch | work zone warning status |
|---|
| City of Bowling Green ITS Field Devices | City of Bowling Green Maintenance Dispatch | work zone warning status |
|---|
| City of Bowling Green ITS Field Devices | City of Bowling Green Public Works Dispatch | work zone warning status |
|---|
| City of Bowling Green ITS Field Devices | City of Bowling Green Traffic Signal System | roadway warning system status |
|---|
| City of Bowling Green Maintenance Dispatch | City of Bowling Green ITS Field Devices | work zone warning device control |
|---|
| City of Bowling Green Public Works Dispatch | City of Bowling Green ITS Field Devices | work zone warning device control |
|---|
| City of Bowling Green Traffic Signal System | City of Bowling Green ITS Field Devices | roadway warning system control |
|---|
| City of Toledo ITS Field Devices | City of Toledo Maintenance Dispatch (CLIC) | work zone warning status |
|---|
| City of Toledo ITS Field Devices | City of Toledo Traffic Management System | roadway warning system status |
|---|
| City of Toledo Maintenance Dispatch (CLIC) | City of Toledo ITS Field Devices | work zone warning device control |
|---|
| City of Toledo Traffic Management System | City of Toledo ITS Field Devices | roadway warning system control |
|---|
| Lucas County Engineer Dispatch | Lucas County ITS Field Devices | work zone warning device control |
|---|
| Lucas County ITS Field Devices | Lucas County Engineer Dispatch | work zone warning status |
|---|
| Lucas County ITS Field Devices | Lucas County Traffic Signal System | roadway warning system status |
|---|
| Lucas County Traffic Signal System | Lucas County ITS Field Devices | roadway warning system control |
|---|
| MDOT ITS Field Equipment | MDOT Statewide TMC | lane management information |
|---|
| Municipal ITS Field Devices | Municipal Maintenance Dispatch | work zone warning status |
|---|
| Municipal ITS Field Devices | Municipal Traffic Signal Systems | roadway warning system status |
|---|
| Municipal Maintenance Dispatch | Municipal ITS Field Devices | work zone warning device control |
|---|
| Municipal Traffic Signal Systems | Municipal ITS Field Devices | roadway warning system control |
|---|
| ODOT ATMS | ODOT District 2 DMS | roadway warning system control |
|---|
| ODOT ATMS | ODOT District 2 Speed Monitoring Roadside Equipment | speed monitoring control |
|---|
| ODOT District 2 CCTV Cameras | ODOT District 2 Office | roadway warning system status |
|---|
| ODOT District 2 DMS | ODOT ATMS | lane management information |
|---|
| ODOT District 2 DMS | ODOT ATMS | roadway warning system status |
|---|
| ODOT District 2 DMS | ODOT District 2 Maintenance Garages | work zone warning status |
|---|
| ODOT District 2 Lane Control Devices | ODOT ATMS | lane management information |
|---|
| ODOT District 2 Maintenance Garages | ODOT District 2 Speed Monitoring Roadside Equipment | speed monitoring control |
|---|
| ODOT District 2 Office | ODOT District 2 CCTV Cameras | roadway warning system control |
|---|
| ODOT District 2 Office | ODOT District 2 Speed Monitoring Roadside Equipment | speed monitoring control |
|---|
| ODOT District 2 RWIS Stations | ODOT District 2 Variable Speed Limit Signs | roadway warning coordination |
|---|
| ODOT District 2 Speed Monitoring Roadside Equipment | ODOT ATMS | speed monitoring information |
|---|
| ODOT District 2 Speed Monitoring Roadside Equipment | ODOT District 2 Maintenance Garages | speed monitoring information |
|---|
| ODOT District 2 Speed Monitoring Roadside Equipment | ODOT District 2 Office | speed monitoring information |
|---|
| ODOT District 2 Variable Speed Limit Signs | ODOT District 2 RWIS Stations | roadway warning coordination |
|---|
| OTIC Central Dispatch | OTIC Queue Warning Detection and Warning System | roadway warning system control |
|---|
| OTIC Queue Warning Detection and Warning System | OTIC Central Dispatch | roadway warning system status |
|---|
| Wood County ITS Field Devices | Wood County Maintenance Dispatch | work zone warning status |
|---|
| Wood County Maintenance Dispatch | Wood County ITS Field Devices | work zone warning device control |
|---|