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

do not prescribe content of return packets #17

Open
gernotheiser opened this issue Mar 14, 2023 · 2 comments
Open

do not prescribe content of return packets #17

gernotheiser opened this issue Mar 14, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@gernotheiser
Copy link

the client should have freedom to change the contents of data. I suggest the following minimum packet content rule.

Layout: |w[0]|w[1]|...|w[n-2]|w[n-1]|

Content:
w[0]: sequence number
w[1]...w[n-2]: sender-defined
w[n-1]: checksum of w[0]...w[n-2]

@omeh-a omeh-a added the enhancement New feature or request label Mar 15, 2023
@wom-bat
Copy link
Contributor

wom-bat commented Mar 6, 2024

There is now a 'latency-check' target that enforces w[1] = w[0] + 1

@gernotheiser
Copy link
Author

is there still a checksum test?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants