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 fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Moorhead Traffic Signals=>intersection control status=>West Fargo TOC Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT Traffic Signals=>intersection control status=>Fargo Traffic Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Fargo Traffic Signals=>intersection control status=>NDDOT Traffic Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Fargo Traffic Signals=>intersection control status=>West Fargo TOC Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Fargo Traffic Signals=>intersection control status=>FM Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | MnDOT D4 Traffic Signals=>intersection control status=>Fargo Traffic Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | MnDOT D4 Traffic Signals=>intersection control status=>West Fargo TOC Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Moorhead Traffic Signals=>intersection control status=>Fargo Traffic Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | Moorhead Traffic Signals=>intersection control status=>FM Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | West Fargo TOC Signals=>intersection control status=>NDDOT Traffic Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | West Fargo TOC Signals=>intersection control status=>Fargo Traffic Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | West Fargo TOC Signals=>intersection control status=>FM Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | FM Signals=>intersection control status=>Fargo Traffic Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | FM Signals=>intersection control status=>West Fargo TOC Signals |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | MnDOT D4 Traffic Signals=>intersection control status=>FM Signals |
|---|
| 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 |
|---|
| Fargo TOC | Fargo Traffic Signals | intersection management application info |
|---|
| Fargo TOC | NDDOT Traffic Signals | intersection management application info |
|---|
| Fargo TOC | West Fargo TOC Signals | intersection management application info |
|---|
| Fargo Traffic Signals | Fargo TOC | signal control status |
|---|
| Fargo Traffic Signals | FM Signals | intersection control status |
|---|
| Fargo Traffic Signals | FM TOC | signal control status |
|---|
| Fargo Traffic Signals | NDDOT TOC | signal control status |
|---|
| Fargo Traffic Signals | NDDOT Traffic Signals | intersection control status |
|---|
| Fargo Traffic Signals | West Fargo TOC Signals | intersection control status |
|---|
| FM Signals | Fargo Traffic Signals | intersection control status |
|---|
| FM Signals | FM TOC | signal control status |
|---|
| FM Signals | West Fargo TOC Signals | intersection control status |
|---|
| FM TOC | FM Signals | intersection management application info |
|---|
| FM TOC | West Fargo TOC Signals | intersection management application info |
|---|
| MnDOT D4 TOC | Fargo Traffic Signals | intersection management application info |
|---|
| MnDOT D4 TOC | West Fargo TOC Signals | intersection management application info |
|---|
| MnDOT D4 Traffic Signals | Fargo Traffic Signals | intersection control status |
|---|
| MnDOT D4 Traffic Signals | FM Signals | intersection control status |
|---|
| MnDOT D4 Traffic Signals | MnDOT D4 TOC | signal control status |
|---|
| MnDOT D4 Traffic Signals | MnTOC | signal control status |
|---|
| MnDOT D4 Traffic Signals | West Fargo TOC Signals | intersection control status |
|---|
| MnTOC | Fargo Traffic Signals | intersection management application info |
|---|
| MnTOC | West Fargo TOC Signals | intersection management application info |
|---|
| Moorhead TOC | Fargo Traffic Signals | intersection management application info |
|---|
| Moorhead TOC | West Fargo TOC Signals | intersection management application info |
|---|
| Moorhead Traffic Signals | Fargo Traffic Signals | intersection control status |
|---|
| Moorhead Traffic Signals | FM Signals | intersection control status |
|---|
| Moorhead Traffic Signals | MnTOC | signal control status |
|---|
| Moorhead Traffic Signals | Moorhead TOC | signal control status |
|---|
| Moorhead Traffic Signals | West Fargo TOC Signals | intersection control status |
|---|
| NDDOT TOC | Fargo Traffic Signals | intersection management application info |
|---|
| NDDOT TOC | NDDOT Traffic Signals | intersection management application info |
|---|
| NDDOT Traffic Signals | Fargo Traffic Signals | intersection control status |
|---|
| NDDOT Traffic Signals | NDDOT TOC | signal control status |
|---|
| West Fargo TOC | Fargo Traffic Signals | intersection management application info |
|---|
| West Fargo TOC | FM Signals | intersection management application info |
|---|
| West Fargo TOC | NDDOT Traffic Signals | intersection management application info |
|---|
| West Fargo TOC | West Fargo TOC Signals | intersection management application info |
|---|
| West Fargo TOC Signals | Fargo Traffic Signals | intersection control status |
|---|
| West Fargo TOC Signals | FM Signals | intersection control status |
|---|
| West Fargo TOC Signals | NDDOT Traffic Signals | intersection control status |
|---|
| West Fargo TOC Signals | West Fargo TOC | signal control status |
|---|