US: TMDD - NTCIP Messaging
Description:
This solution is used within the U.S.. It combines standards associated with US: TMDD with those for C-C: NTCIP Messaging. The US: TMDD standards include upper-layer standards required to implement center-to-center communications with traffic management systems. The C-C: NTCIP Messaging standards include lower-layer standards that support partially secure communications between two centers as commonly used in the US.Relevant Regions:
- United States
Comm Profile: C-C: NTCIP Messaging
Comm Class: WAN - Wide Area Network
Standards in Profile:
| Level | Standard |
|---|---|
| Access | Internet Subnet Alternatives |
| Facilities | NTCIP C2C Alternatives |
| Mgmt | Bundle: SNMPv3 MIB |
| Mgmt | W3C WSDL |
| Security | Secure Session Alternatives |
| TransNet | IETF RFC 9293 TCP |
| TransNet | IP Alternatives |
Data Profile: US: TMDD
Standards in Profile:
| Level | Standard |
|---|---|
| Facilities | ITE TMDD Vol 2 |
| ITS Application Entity | ITE TMDD Vol 2 |
Solution Issues Severity: 10
The severity issue score calculation only includes issues associated with standards that are included by default.
Solution Issues:
| Default | Severity | Name | Type | Description |
|---|---|---|---|---|
| True | Low | Inadequate guidance for complex data design | ITS Info Gap | The standard provides a robust design, but there may be more than one way to convey the information contained in this information flow and the standard provides little or no guidance on how to use the defined structures. |
| True | Medium | Out of date (medium) | Standardization Gap | 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. |
| True | Medium | Performance not fully defined (medium) | ITS Info Gap | The performance rules are not fully defined for this information flow. |
| True | Medium | Secure data access not provided | Security Gap | The solution does not define rules on how the application entity authenticates requests to accept or provide data. |
| False | Medium | Option not standardized | Standardization Gap | The option set includes at least one option that is not (yet) defined in a standard. |
| False | Medium | Uncertainty about trust revocation mechanism | Security Gap | The mechanisms used to prevent bad actors from sending authorized messages is unproven. |
Solution to Triples
This solution is used on the following information flow triples: