-
Notifications
You must be signed in to change notification settings - Fork 0
Issues: sctplab/pr-sctp-improved
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
sid/ssn values are reported multiple times in one FORWARD-TSN Chunk
enhancement
#17
opened Dec 13, 2016 by
TheAomx
INIT-Chunk with cropped FORWARD-TSN-supported parameter is accepted
bug
#16
opened Dec 12, 2016 by
TheAomx
Upon receipt of invalid FORWARD-TSN-Chunk with too long tlv-value no ABORT-Chunk is sent
bug
#14
opened Dec 12, 2016 by
TheAomx
Incoming SACK-Chunks are allowed when NR-SACK-Chunks are listed at the supported-extensions
bug
#13
opened Dec 12, 2016 by
TheAomx
Information in nr_gap-Blocks in NR-SACK-Chunks are not used optimally
enhancement
#11
opened Dec 12, 2016 by
TheAomx
Already abandoned user messages are not discarded as early as possible
enhancement
#9
opened Dec 12, 2016 by
TheAomx
I-FORWARD-TSN-Chunk is used although support has not been indicated by both endpoints
bug
#7
opened Dec 12, 2016 by
TheAomx
I-FORWARD-TSN-Chunk is accepted when no I-DATA-Support is announced at handshake
bug
#6
opened Dec 12, 2016 by
TheAomx
Unordered user message is not delivered if two FORWARD-TSN-Chunks are bundled
bug
#4
opened Dec 12, 2016 by
TheAomx
Unordered user messages can not be received out of order
enhancement
#3
opened Dec 12, 2016 by
TheAomx
The Forward-TSN-supported parameter is not listed at the unrecognized parameters
bug
#2
opened Dec 12, 2016 by
TheAomx
ProTip!
What’s not been updated in a month: updated:<2024-10-05.