RFC 6458 (SCTP socket API) Issues

Section 3.2 Non-Blocking Mode

• … by the SCTP_ASSOC_CHANGE event with SCTP_COMM_UP or SCTP_CANT_START_ASSOC. If user data could not be sent (due to an SCTP_CANT_START_ASSOC),…
• Errata 6112

Section 6.1.1 SCTP_ASSOC_CHANGE

• sac_info: If sac_state is SCTP_COMM_LOST or SCTP_CANT_STR_ASSOC and an ABORT chunk was…
• Errata 6113

Section 6.1.2 SCTP_PEER_ADDR_CHANGE

• spc_state: A definition for SCTP_ADDR_CONFIRMED is missing. This is supported by FreeBSD and Linux, not by Solaris (yet).
• Errata 6116

Section 6.1.7 SCTP_PARTIAL_DELIVERY_EVENT

• uint16_t pdapi_stream;
• uint16_t pdapi_seq;
• Linux and Solaris implement it using uint32_t as specified, allthough uint16_t makes sense. FreeBSD uses uint16_t.

Section 8.2.1 SCTP_STATUS

• SCTP_BOUND doesn't make sense as an association state.
• Errata 6115

Section 9.5 sctp_getladdrs()

• If the id field is set to the value SCTP_FUTURE_ASSOC, then the locally bound…
• Errata 6114

Appendix A/B

• The client uses IPv4 and the server IPv6 sockets. In case of IPv6 sockets are IPv6 only, they can't interoperate.