rfc_6458_sctp_socket_api_issues
RFC 6458 (SCTP socket API) Issues
Section 3.2 Non-Blocking Mode
- … by the
SCTP_ASSOC_CHANGEevent withSCTP_COMM_UPorSCTP_CANT_START_ASSOC. If user data could not be sent (due to anSCTP_CANT_START_ASSOC),…
Section 6.1.1 SCTP_ASSOC_CHANGE
sac_info: Ifsac_stateisSCTP_COMM_LOSTorSCTP_CANT_STR_ASSOCand an ABORT chunk was…
Section 6.1.2 SCTP_PEER_ADDR_CHANGE
spc_state: A definition forSCTP_ADDR_CONFIRMEDis 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;- Linux and Solaris implement it using
uint32_tas specified, allthoughuint16_tmakes sense. FreeBSD usesuint16_t.
Section 8.2.1 SCTP_STATUS
SCTP_BOUNDdoesn't make sense as an association state.
Section 9.5 sctp_getladdrs()
- If the
idfield is set to the valueSCTP_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.txt · Last modified: by tuexen
