This solution is used within the U.S.. It combines standards associated with US: WZDx with those for I–I: Secure Internet (ITS). The US: WZDx standards include upper–layer standards required to implement work zone information data exchanges. The I–I: Secure Internet (ITS) standards include lower–layer standards that support secure communications between ITS equipment using X.509 or IEEE 1609.2 security certificates.
| Level | DocNum | FullName | Description |
|---|
| 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 5280 | Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile | This standard (RFC) defines how to use X.509 certificates for secure communications over the Internet. |
|---|
| Security | IETF RFC 8446 | The Transport Layer Security (TLS) Protocol | This standard (RFC) specifies Version 1.3 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. |
|---|
| ITS Application Entity | WZDx | Work Zone Data Exchange | This standard defines a common format for exchanging work zone information. |
|---|
| Facilities | IETF RFC 7159 | The JavaScript Object Notation (JSON) Data Interchange Format | The JavaScript Object Notation (JSON), a lightweight, text–based, language–independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data. This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience–based interoperability guidance. |
|---|
| Facilities | IETF RFC 7230 | Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing | This standard (RFC) defines the main Application Layer protocol used for the world–wide web. |
|---|
| 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 | | Internet Subnet Alternatives | A set of alternative standards that includes any Subnet Layer method of connecting to the Internet. |
|---|
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) | MTDOT Operations Center=>work zone information=>NDDOT Maintenance Management |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT District Maintenance=>work zone information=>Media |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT District Maintenance=>work zone information=>NDDOT RCRS |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT District Maintenance=>work zone information=>NDDOT Maintenance Management |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT District Traffic=>work zone information=>Media |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT District Traffic=>work zone information=>NDDOT RCRS |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT Maintenance Management=>work zone information=>ND Emergency Management Center |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | MnDOT Operations Center=>work zone information=>NDDOT Maintenance Management |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT Maintenance Management=>work zone information=>MnDOT Operations Center |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT Maintenance Management=>work zone information=>SDDOT Operations Center |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT Maintenance Management=>work zone information=>MTDOT Operations Center |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT Maintenance Management=>work zone information=>Media |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT Maintenance Management=>work zone information=>NDDOT RCRS |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT Maintenance Management=>work zone information=>State Radio |
|---|
| Data not fully defined (medium) | Medium | Some of the data elements for this information flow are not fully defined. | (None) | NDDOT District Traffic=>work zone information=>NDDOT Maintenance Management |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT Maintenance Management=>work zone information=>Media |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT Maintenance Management=>work zone information=>ND Emergency Management Center |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT District Traffic=>work zone information=>NDDOT Maintenance Management |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT District Maintenance=>work zone information=>Media |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT District Maintenance=>work zone information=>NDDOT RCRS |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT District Maintenance=>work zone information=>NDDOT Maintenance Management |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT District Traffic=>current infrastructure restrictions=>NDHP Motor Carrier Operations |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT Maintenance Management=>work zone information=>State Radio |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT District Traffic=>work zone information=>NDDOT RCRS |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT Maintenance Management=>work zone information=>NDDOT RCRS |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | MnDOT Operations Center=>work zone information=>NDDOT Maintenance Management |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | MTDOT Operations Center=>work zone information=>NDDOT Maintenance Management |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT Maintenance Management=>current infrastructure restrictions=>NDHP Motor Carrier Operations |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT Maintenance Management=>work zone information=>MnDOT Operations Center |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT Maintenance Management=>work zone information=>SDDOT Operations Center |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT Maintenance Management=>work zone information=>MTDOT Operations Center |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | NDDOT District Traffic=>work zone information=>Media |
|---|
| Performance not fully defined (medium) | Medium | The performance rules are not fully defined for this information flow. | (None) | (All) |
|---|
| Secure data access not provided | Medium | The solution does not define rules on how the application entity authenticates requests to accept or provide data. | (None) | (All) |
|---|
| Not a standard (minor) | Low | The document is publicly available and widely used but it is not currently a formal standard. | (None) | (All) |
|---|