-
Notifications
You must be signed in to change notification settings - Fork 1
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
Want built-in field validation mechanisms #2
Comments
@zeeshanlakhani and I talked this over earlier -- to some extent this going to be key for IGMP because we want to catch and validate far more application-level facets of input data in keeping with the spec (and to do this with as little manual effort as possible). There are a couple of things to keep in mind.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, consumers such as OPTE need to manually check certain header validity properties on parsed packets -- mainly IP and Geneve version fields. It would be nice to include these as part of the packet definition, and factor them into (de)parsing.
These should be optional -- ideally parsed packets which pass muster would have this represented as a distinct typestate.
The text was updated successfully, but these errors were encountered: