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

verifyChecksum semantics #360

Closed
cc10512 opened this issue Jul 25, 2017 · 3 comments
Closed

verifyChecksum semantics #360

cc10512 opened this issue Jul 25, 2017 · 3 comments

Comments

@cc10512
Copy link
Contributor

cc10512 commented Jul 25, 2017

No description provided.

@jafingerhut
Copy link
Collaborator

With recent commits to the PSA spec, I think this issue has been resolved with the following answers: There is no separate verifyChecksum control block in PSA. All (or at least most) checking of header checksums is expected to be performed in the parsers, setting some kind of result for use in the following Ingress or Egress control block, such as the parser error. The Ingress and Egress control blocks are expected to check for parser errors, if desired, and then also perform the desired actions on packets that experienced errors during parsing.

This issue can be closed then, I think?

@jafingerhut
Copy link
Collaborator

@cc10512 I think this issue can be closed now, with recent commits to the draft PSA spec?

@cc10512
Copy link
Contributor Author

cc10512 commented Oct 13, 2017

Agreed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants