RFC Errata
RFC 6458, "Sockets API Extensions for the Stream Control Transmission Protocol (SCTP)", December 2011
Source of RFC: tsvwg (wit)See Also: RFC 6458 w/ inline errata
Errata ID: 6112
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Michael Tuexen
Date Reported: 2020-04-20
Verifier Name: Martin Duke
Date Verified: 2020-04-27
Section 3.2 says:
The success or failure of sending the data message (with possible SCTP_INITMSG ancillary data) will be signaled 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), the sender will also receive an SCTP_SEND_FAILED_EVENT event.
It should say:
The success or failure of sending the data message (with possible SCTP_INITMSG ancillary data) will be signaled by the SCTP_ASSOC_CHANGE event with SCTP_COMM_UP or SCTP_CANT_STR_ASSOC. If user data could not be sent (due to an SCTP_CANT_STR_ASSOC), the sender will also receive an SCTP_SEND_FAILED_EVENT event.
Notes:
The constant SCTP_CANT_START_ASSOC is not defined. The correct name is SCTP_CANT_STR_ASSOC.