User Tools

Site Tools


rfc_6458_sctp_socket_api_issues

This is an old revision of the document!


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),…

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…

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).

Section 6.1.7 SCTP_PARTIAL_DELIVERY_EVENT

  • uint16_t pdapi_stream;
  • uint16_t pdapi_seq;

Section 8.2.1 SCTP_STATUS

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

Section 9.5 sctp_getladdrs()

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

Appendix A/B

  • The client uses IPv4 and the server IPv6 sockets. In case of IPv6 sockets are IPv6 only, they can't interoperate.
rfc_6458_sctp_socket_api_issues.1587397015.txt.gz · Last modified: by tuexen