This solution is used within the U.S.. It combines standards associated with US: NTCIP Message Sign with those for I–F: SNMPv3/TLS. The US: NTCIP Message Sign standards include upper–layer standards required to implement center–to–field message sign 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 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 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.
Source | Destination | Flow |
---|
ACAA Field Devices | ACAA Offices | roadway dynamic signage status |
---|
ACAA Offices | ACAA Field Devices | roadway dynamic signage data |
---|
City of Pittsburgh Field Devices | City of Pittsburgh Traffic Management Center (CityTMC) | roadway dynamic signage status |
---|
City of Pittsburgh Traffic Management Center (CityTMC) | City of Pittsburgh Field Devices | lane management control |
---|
City of Pittsburgh Traffic Management Center (CityTMC) | City of Pittsburgh Field Devices | roadway dynamic signage data |
---|
Park–n–Ride Facilities | PennDOT Field Devices – District | roadway dynamic signage data |
---|
PennDOT County Maintenance Offices | PennDOT Field Devices – District | roadway dynamic signage data |
---|
PennDOT District Ten Offices | PennDOT Field Devices – District | roadway dynamic signage data |
---|
PennDOT District Twelve Offices | PennDOT Field Devices – District | roadway dynamic signage data |
---|
PennDOT Field Devices – District | ACAA Offices | roadway dynamic signage status |
---|
PennDOT Field Devices – District | Park–n–Ride Facilities | roadway dynamic signage status |
---|
PennDOT Field Devices – District | PennDOT County Maintenance Offices | roadway dynamic signage status |
---|
PennDOT Field Devices – District | PennDOT District Eleven Offices | roadway dynamic signage status |
---|
PennDOT Field Devices – District | PennDOT District Twelve Offices | roadway dynamic signage status |
---|
PennDOT Field Devices – District | Western Region Traffic Management Center (PennDOT) | roadway dynamic signage status |
---|
PennDOT Field Devices – District One | Adjacent PennDOT District Offices | roadway dynamic signage status |
---|
PennDOT Field Devices – District One | Western Region Traffic Management Center (PennDOT) | roadway dynamic signage status |
---|
Western Region Traffic Management Center (PennDOT) | PennDOT Field Devices – District | roadway dynamic signage data |
---|
Western Region Traffic Management Center (PennDOT) | PennDOT Field Devices – District One | roadway dynamic signage data |
---|