Skip to content
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

Create network_port_object.py #257

Closed
wants to merge 2 commits into from
Closed

Create network_port_object.py #257

wants to merge 2 commits into from

Conversation

tjohnsonhvac
Copy link

Here are the definition for the NetworkPortObject.

The optional properties for this are not always optional depending on other properties defined. How should that be handled?

Here are the definition for the NetworkPortObject.
* I had a question on the data type on line #112

The optional properties for this are not always optional depending on other properties defined. How should that be handled?
@JoelBender
Copy link
Owner

There is no generalized framework for validating objects, i.e., checking to make sure that all required properties are defined and checking for proper combinations of optional ones. For now if a property has an 'O' in the Conformance Code column that is enough.

There are some additional unsigned properties with value restrictions (like Max_Master is 0..127, Priority_For_Writing is 1..16, AccessThreatLevel is 0..100) and it would be nice to handle these consistently, I think this is going in the right direction.

There are choices and sequences that are context encoded (the number in brackets in the ASN.1 notation) that need to be added to the new things in the base types.

added property number comments from standard.
@JoelBender
Copy link
Owner

Merged into 15-network-port-object

@JoelBender JoelBender closed this Mar 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants