Skip to content

Latest commit

 

History

History
36 lines (32 loc) · 5.38 KB

README.md

File metadata and controls

36 lines (32 loc) · 5.38 KB
Raw

Status of the Association Termination Tests

The following table show the current status of the Implementation. Once the implementation is completed, the implementation specific columns will be removed.

Name Implemented Finalized OS specific Result FreeBSD Result Linux
sctp-at-v-2-2 Yes Yes No Passed Passed
sctp-at-i-2-3 Yes Yes No Passed Passed
sctp-at-i-2-4 Yes Yes No Passed Passed
sctp-at-i-2-5 Yes (Note 1) Yes No Passed (Note 2) Passed
sctp-at-v-2-6 Yes Yes No Passed Failed (Note 3)
sctp-at-i-2-7-1 Yes (Note 4) Yes No Passed Passed
sctp-at-i-2-7-2 Yes (Note 5) Yes No Passed (Note 6) Passed
sctp-at-i-2-7-3 Yes (Note 7) Yes No Passed Passed
sctp-at-i-2-7-4 Yes (Note 8) Yes No Passed Passed
sctp-at-i-2-8 Yes Yes Yes (Note 9) Passed Passed
sctp-at-i-2-9 Yes (Note 10) Yes No Passed Passed
sctp-at-i-2-10 Yes Yes No Passed Passed
sctp-at-i-2-11 Yes Yes No Passed Passed
sctp-at-i-2-12 Yes (Note 11) Yes No Passed Passed
sctp-at-i-2-13 Yes Yes No Passed Passed
sctp-at-v-2-14 Yes Yes No Passed Passed

Notes

  1. When the shutdown guard timer runs off, Linux reports ETIMEDOUT and FreeBSD reports ECONNABORTED at the socket layer in errno (similar to Note 11).
  2. Fix for sctp-at-i-2-5: r287294.
  3. Once the association has been terminated on a connected non-blocking 1-to-1 style socket, read() returns -1 indicating "Resource temporarily unavailable" instead of 0. See Note 6 on README.
  4. When calling write() after shutdown(, SHUT_WR), Linux reports ESHUTDOWN whereas FreeBSD reports ECONNRESET. Shouldn't EPIPE be reported?
  5. When the association is in SHUTDOWN-RECEIVED state and write() is called, Linux reports ESHUTDOWN whereas FreeBSD reports ECONNRESET. Shouldn't EPIPE be reported?
  6. Fix for sctp-at-i-2-7-2: r287444.
  7. When the association is in SHUTDOWN-PENDING state and write() is called, Linux reports ESHUTDOWN whereas FreeBSD reports ECONNRESET. Shouldn't EPIPE be reported?
  8. When the association is in SHUTDOWN-ACK-SENT state and write() is called, Linux reports ESHUTDOWN whereas FreeBSD reports ECONNRESET. Shouldn't EPIPE be reported?
  9. Linux bundles a SACK with the SHUTDOWN, even if not necessary based on TSNs.
  10. Not sure where it is specified that DATA chunks after SHUTDOWN chunk needs to be discarded. Looks like a protocol violation to me.
  11. After more than Max.Assoc.Retrans retransmissions, FreeBSD reports ECONNABORTED whereas Linux reports ETIMEDOUT (similar to Note 1).