METR: Discrepancy Reporting Requirements - Apache Kafka
Description:
This solution is used within the U.S.. It combines standards associated with METR: Discrepancy Reporting Requirements with those for Apache Kafka. The METR: Discrepancy Reporting Requirements standards include upper-layer standards required to exchange traffic regulation discrepancies with a discrepancy handling center. The Apache Kafka standards include lower-layer open source code that supports data distribution of specific types of data.Relevant Regions:
- United States
Comm Profile: Apache Kafka
Comm Class: WAN - Wide Area Network
Standards in Profile:
Level | Standard |
---|---|
Access | Internet Subnet Alternatives |
Facilities | Apache Kafka |
Facilities | Apache Zookeeper |
Mgmt | Apache Zookeeper |
Security | IETF RFC 8446 TLS |
TransNet | IETF RFC 9293 TCP |
TransNet | IP Alternatives |
Data Profile: METR: Discrepancy Reporting Requirements
Standards in Profile:
Level | Standard |
---|---|
ITS Application Entity | ISO 24315 METR Data Req'ts |
ITS Application Entity | ISO 24315 METR Discrepancy Handling SR |
Solution Issues Severity: 23
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 | 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. |
Solution to Triples
This solution is used on the following information flow triples: