(None-Data) - OASIS MQTT
Description:
This solution is used within Australia and the U.S.. It combines standards associated with (None-Data) with those for OASIS MQTT. The (None-Data) standards include an unspecified set of standards at the upper layers. The OASIS MQTT standards include lower-layer standards that support data distribution of specific types of data.Relevant Regions:
- Australia
- United States
Comm Profile: OASIS MQTT
Comm Class: WAN - Wide Area Network
Standards in Profile:
| Level | Standard |
|---|---|
| Access | Internet Subnet Alternatives |
| Facilities | OASIS Message Queueing Telemetry Transport (MQTT) |
| Mgmt | OASIS MQTT Device Management Protocol |
| Security | IP Security Alternatives |
| Security | OASIS Message Queueing Telemetry Transport (MQTT) |
| TransNet | Internet Transport Alternatives |
| TransNet | IP Alternatives |
Data Profile: (None-Data)
Standards in Profile:
- None
Solution Issues Severity: 42
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 | Overlap of standards (Minor) | Overlap | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. However, as this information transfer is infrastructure-based, agencies can deploy a solution throughout their jurisdiction with minimal downside and can use gateways to connect to other technologies. |
| 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 | Security inadequate | Security Gap | The solution does not provide adequate communications security for the information triple, which potentially jeopardizes C-ITS operations. |
| True | Medium | Unvetted by community | Standardization Gap | The proposed solution uses a suite of standards that is accepted within some communities, but has not necessarily been accepted for use within the context of this information triple. |
| True | Ultra | Data profile not defined | Data Profile Gap | Performance, functionality, and the upper-layers of the OSI stack have not been defined for this information flow. |
Solution to Triples
This solution is used on the following information flow triples: