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

Reduce MAX_SEQUENCE_PER_ROUND from 1024 to 512 #1067

Closed
fujiapple852 opened this issue Mar 24, 2024 · 0 comments · Fixed by #1068
Closed

Reduce MAX_SEQUENCE_PER_ROUND from 1024 to 512 #1067

fujiapple852 opened this issue Mar 24, 2024 · 0 comments · Fixed by #1068
Labels
enhancement New feature or request
Milestone

Comments

@fujiapple852
Copy link
Owner

Reduce MAX_SEQUENCE_PER_ROUND from 1024 to 512

The Dublin multipath strategy for IPv6/udp encodes the sequence number in the payload length and consequently the maximum sequence number must be no larger than the maximum IPv6/udp payload size. It is important that the range of possible sequence numbers is at least BUFFER_SIZE to ensure delayed responses from a prior round are not incorrectly associated with later rounds.

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

Successfully merging a pull request may close this issue.

1 participant