This solution is used within the U.S.. It combines standards associated with US: NTCIP Environmental Sensors with those for I–F: SNMPv3/TLS. The US: NTCIP Environmental Sensors standards include upper–layer standards required to implement center–to–field weather and environmental sensor 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 1204 | NTCIP Environmental Sensor Station Interface Standard | This standard defines SNMP objects (data elements) for monitoring and controlling environmental sensor stations (especially road weather stations). |
---|
Facilities | NTCIP 1204 | NTCIP Environmental Sensor Station Interface Standard | This standard defines SNMP objects (data elements) for monitoring and controlling environmental sensor stations (especially road weather stations). |
---|
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 |
---|
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) |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | ODOT District 4 RWIS Stations=>environmental sensor data=>ODOT Connected Vehicles Roadside Equipment |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | City of Green High Water Warning Systems=>environmental sensor data=>City of Green Traffic Operations Center |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | City of Green RWIS Stations=>environmental sensor data=>City of Green Maintenance Dispatch |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | City of Kent RWIS Stations=>environmental sensor data=>City of Kent Maintenance Dispatch |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | ODOT District 4 RWIS Stations=>environmental sensor data=>ODOT ATMS |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | ODOT District 4 RWIS Stations=>environmental sensor data=>ODOT District 4 Maintenance Garages |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | ODOT District 4 RWIS Stations=>environmental sensor data=>ODOT District 4 Office |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | ODOT District 4 RWIS Stations=>environmental sensor data=>Summit County Maintenance Dispatch |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | Other Municipalities RWIS Stations=>environmental sensor data=>Other Municipalities Maintenance Dispatch |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | Portage County RWIS Stations=>environmental sensor data=>Portage County Maintenance Dispatch |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | City of Akron RWIS Stations=>environmental sensor data=>City of Akron Maintenance Dispatch |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | City of Hudson RWIS Stations=>environmental sensor data=>City of Hudson Maintenance Dispatch |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | City of Barberton High Water Warning Systems=>environmental sensor data=>City of Barberton Traffic Operations Center |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | City of Barberton RWIS Stations=>environmental sensor data=>City of Barberton Maintenance Dispatch |
---|
Accuracy of data | Low | The standard is missing accuracy requirements for some of its data, which may result in anomalous behavior. | (None) | ODOT District 4 RWIS Stations=>environmental sensor data=>Summit County Traffic Operations Center |
---|
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 Akron Maintenance Dispatch | City of Akron RWIS Stations | environmental sensors control |
---|
City of Akron RWIS Stations | City of Akron Maintenance Dispatch | environmental sensor data |
---|
City of Barberton High Water Warning Systems | City of Barberton Traffic Operations Center | environmental sensor data |
---|
City of Barberton Maintenance Dispatch | City of Barberton RWIS Stations | environmental sensors control |
---|
City of Barberton RWIS Stations | City of Barberton Maintenance Dispatch | environmental sensor data |
---|
City of Barberton Traffic Operations Center | City of Barberton High Water Warning Systems | environmental sensors control |
---|
City of Green High Water Warning Systems | City of Green Traffic Operations Center | environmental sensor data |
---|
City of Green Maintenance Dispatch | City of Green RWIS Stations | environmental sensors control |
---|
City of Green RWIS Stations | City of Green Maintenance Dispatch | environmental sensor data |
---|
City of Green Traffic Operations Center | City of Green High Water Warning Systems | environmental sensors control |
---|
City of Hudson Maintenance Dispatch | City of Hudson RWIS Stations | environmental sensors control |
---|
City of Hudson RWIS Stations | City of Hudson Maintenance Dispatch | environmental sensor data |
---|
City of Kent Maintenance Dispatch | City of Kent RWIS Stations | environmental sensors control |
---|
City of Kent RWIS Stations | City of Kent Maintenance Dispatch | environmental sensor data |
---|
ODOT ATMS | ODOT District 4 RWIS Stations | environmental sensors control |
---|
ODOT District 4 Maintenance Garages | ODOT District 4 RWIS Stations | environmental sensors control |
---|
ODOT District 4 Office | ODOT District 4 RWIS Stations | environmental sensors control |
---|
ODOT District 4 RWIS Stations | ODOT ATMS | environmental sensor data |
---|
ODOT District 4 RWIS Stations | ODOT Connected Vehicles Roadside Equipment | environmental sensor data |
---|
ODOT District 4 RWIS Stations | ODOT District 4 Maintenance Garages | environmental sensor data |
---|
ODOT District 4 RWIS Stations | ODOT District 4 Office | environmental sensor data |
---|
ODOT District 4 RWIS Stations | ODOT District 4 Variable Speed Limit Signs | environmental sensor coordination |
---|
ODOT District 4 RWIS Stations | Summit County Maintenance Dispatch | environmental sensor data |
---|
ODOT District 4 RWIS Stations | Summit County Traffic Operations Center | environmental sensor data |
---|
ODOT District 4 Variable Speed Limit Signs | ODOT District 4 RWIS Stations | environmental sensor coordination |
---|
Other Municipalities Maintenance Dispatch | Other Municipalities RWIS Stations | environmental sensors control |
---|
Other Municipalities RWIS Stations | Other Municipalities Maintenance Dispatch | environmental sensor data |
---|
Portage County Maintenance Dispatch | Portage County RWIS Stations | environmental sensors control |
---|
Portage County RWIS Stations | Portage County Maintenance Dispatch | environmental sensor data |
---|