METR: Distribution Requirements - OASIS MQTT over Wireless
Description:
This solution is used within Canada and the U.S.. It combines standards associated with METR: Distribution Requirements with those for OASIS MQTT over Wireless. The METR: Distribution Requirements standards include upper-layer standards required to distribute traffic regulations from a distribution center. The OASIS MQTT over Wireless standards include lower-layer standards that support data distribution of specific types of data over wireless links.Relevant Regions:
- Canada
- United States
Comm Profile: OASIS MQTT over Wireless
Comm Class: WAN - Wide Area Network
Standards in Profile:
| Level | Standard |
|---|---|
| Access | Wireless Internet Alternatives (NA) |
| 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: METR: Distribution Requirements
Standards in Profile:
| Level | Standard |
|---|---|
| ITS Application Entity | ISO 24315 METR Data Req'ts |
| ITS Application Entity | ISO 24315 METR Distribution SR |
Solution Issues Severity: 34
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 | High | Draft not available (Critical) | Standardization Gap | The standards development organization has established a work item for the subject standard but a draft is not available for this critical feature to enable the interface. The draft may be missing due to the work item being new or simply a lack of activity on the work item. |
| False | Medium | Overlap of standards | 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. |
| False | Medium | Regulatory Permission Needed | Standardization Gap | Deployment of this standard requires regulatory approval, which is currently subject to significant delays. |
| False | High | Regulatory Issue | Standardization Gap | Deployment of this standard is subject to regulatory approval, which is not currently expected to be granted for deployments in the near-term. |
Solution to Triples
This solution is used on the following information flow triples: