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

FreeBSD accept OUTGOING_SSN_RESET as successful acknowledment for OUTGOING_SSN_RESET and ADD_OUTGOING_STREAMS #39

Open
hoelscher opened this issue Jun 6, 2016 · 0 comments

Comments

@hoelscher
Copy link

hoelscher commented Jun 6, 2016

The RFC 6525 says for the resp_sn field in Outgoing SSN Reset Request parameter, that an endpoint who receives it, must mark the request sequence number as acknowledged and stop if nessesary the reconfig Timer. There is no word for performing the whole actions like when receiving a reconfig response. FreeBSD performes the reset like OUTGOING SSN RESET when receiving an OUTGOING SSN RESET with the response sequence number for a OUTGOING SSN RESET. If the response sequence number belongs to an ADD OUTGOING STREAMS Request, FreeBSD adds the new streams.
That is a problem is a Response with a deny is lost on wire or a new OUTGOING SSN RESET is faster than the response. So the SUT performes a requests which is nor successful performed.
see test
https://github.com/nplab/RFC6525_Testsuite/blob/master/implementation_tests/sctp-sr-i-mf/sctp-sr-i-mf-i-5-1.pkt
https://github.com/nplab/RFC6525_Testsuite/blob/master/implementation_tests/sctp-sr-i-mf/sctp-sr-i-mf-i-5-3.pkt

@tuexen tuexen added this to the Implementation of RFC6525 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