Data for Distribution (TBD) - OASIS AMQP over Wireless
Description:
This solution is used within Canada, the E.U. and the U.S.. It combines standards associated with Data for Distribution (TBD) with those for OASIS AMQP over Wireless. The Data for Distribution (TBD) standards include a placeholder for upper-layer standards necessary to define the data (elements and structures) necessary to complete a solution for the information flow based on data distribution technologies. The data standard will need to include a specific customization for the desired data distribution technology used (e.g., Kafka, DDS, etc.).. The OASIS AMQP over Wireless standards include lower-layer standards that support data distribution of specific types of data over wireless links.Relevant Regions:
- Canada
- European Union
- United States
Comm Profile: OASIS AMQP over Wireless
Comm Class: WAN - Wide Area Network
Standards in Profile:
| Level | Standard |
|---|---|
| Access | Wireless Internet Alternatives (NA) |
| Facilities | OASIS Advanced Message Queueing Protocol (AMQP) |
| Security | IP Security Alternatives |
| TransNet | Internet Transport Alternatives |
| TransNet | IP Alternatives |
Data Profile: Data for Distribution (TBD)
Standards in Profile:
Solution Issues Severity: 61
The severity issue score calculation only includes issues associated with standards that are included by default.
Solution Issues:
| Default | Severity | Name | Type | Description |
|---|---|---|---|---|
| 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. |
| 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 | Still under development | Standardization Gap | A draft of the standard has been developed by the working group, but it was still under development at the time this analysis was performed. |
| 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. |
| 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. |