-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maintain IEEE 1609.2 Security Headers #543
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update msgRepeatOptions value
Kafka version update
…ines merged. Currently only support BSM for both
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Details
Description
Includes updates to both the UDP endpoints and the log ingest endpoint to ensure ASN.1 encoded messages are recorded in Kafka with the IEEE 1609.2 security headers on them (when present).
The log ingestion no longer deposits J2735 message types directly to the topic.Asn1DecoderInput topic, instead routes the messages depending upon their message type to the corresponding topic.OdeRawEncodedXJson topic.
The UDP endpoints now build out proper OdeData objects before depositing ASN.1 messages to their corresponding topic.OdeRawEncodedXJson topic. This is to ensure all data within the RawEncoded topics conform to the same message structure.
Everything downstream from the RawEncoded topics remain unaffected by these changes. (topic.Asn1DecoderInput and beyond)
Related Issue
N/A
Motivation and Context
How Has This Been Tested?
Types of changes
Checklist:
ODE Contributing Guide