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

setsockopt SCTP_RESET_STREAMS copies, if all stream_id are in stream_list, to the INCOMING_SSN_RESET request. list on wire should be empty #26

Open
hoelscher opened this issue May 30, 2016 · 0 comments
Milestone

Comments

@hoelscher
Copy link

hoelscher commented May 30, 2016

If an application calls the socketoption SCTP_RESET_STREMS with all existing stream ids for an INCOMING_SSN_RESET request, the implementation sends a requests with all stream ids in the list. If the application calls the syscall for an OUTGOING_SSN_RESET requests, the implementation sends an empty list. This reaction is not a big problem because it results in the same reset of all streams, but a similar reaction of both ways (INCOMIN and OUTGOING requests) would be nice.
see
https://github.com/nplab/RFC6525_Testsuite/blob/master/api_tests/sctp-sr-api-rs/sctp-sr-api-rs-v-6-7.pkt
https://github.com/nplab/RFC6525_Testsuite/blob/master/api_tests/sctp-sr-api-rs/sctp-sr-api-rs-v-6-9.pkt
https://github.com/nplab/RFC6525_Testsuite/blob/master/api_tests/sctp-sr-api-rs/sctp-sr-api-rs-v-6-25.pkt
https://github.com/nplab/RFC6525_Testsuite/blob/master/api_tests/sctp-sr-api-rs/sctp-sr-api-rs-v-6-27.pkt

@tuexen tuexen added this to the SocketAPI milestone Jun 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants