jer: Add JER-specific constraints, fix BIT STRINGs with variable size #192
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
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.
Fixes JER BIT STRINGs with variable sizes as mentioned in #133.
X.697 24.3 mandates that JER BIT STRINGs which do not have a fixed size, should be encoded as, for example,
{"value":"FE","length":7}instead of just"FE".JER-specific constraints, similarly to OER and PER constraints, were introduced to be used with the encoder/decoder. Currently these constraints are composed of only one field associated with the
SIZEconstraint and are only used with BIT STRINGs. They can be extended in the future to include other constraints types or other JER-specific encoding instructions like the use of Base64 in some types.