RFC Errata
Found 6 records.
Status: Verified (6)
RFC 6458, "Sockets API Extensions for the Stream Control Transmission Protocol (SCTP)", December 2011
Source of RFC: tsvwg (wit)
Errata ID: 6111
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Michael Tuexen
Date Reported: 2020-04-20
Verifier Name: Martin Duke
Date Verified: 2020-04-27
Throughout the document, when it says:
in Section 5.3.2
SCTP_EOF: Setting this flag invokes the SCTP graceful shutdown
procedure on the specified association. Graceful shutdown
assures that all data queued by both endpoints is
successfully transmitted before closing the association.
SCTP_SENDALL: This flag, if set, will cause a one-to-many
style socket to send the message to all associations that
are currently established on this socket. For the one-to-
one style socket, this flag has no effect.
in Section 5.3.4
SCTP_EOF: Setting this flag invokes the SCTP graceful shutdown
procedures on the specified association. Graceful shutdown
assures that all data queued by both endpoints is successfully
transmitted before closing the association.
SCTP_SENDALL: This flag, if set, will cause a one-to-many style
socket to send the message to all associations that are
currently established on this socket. For the one-to-one style
socket, this flag has no effect.
in Section 8.1.13
The sinfo_flags field is composed of a bitwise OR
of SCTP_UNORDERED, SCTP_EOF, and SCTP_SENDALL.
in Section 8.1.31
The snd_flags parameter is composed of a bitwise OR
of SCTP_UNORDERED, SCTP_EOF, and SCTP_SENDALL.
It should say:
in Section 5.3.2
SCTP_EOF: Setting this flag invokes the SCTP graceful shutdown
procedure on the specified association. Graceful shutdown
assures that all data queued by both endpoints is
successfully transmitted before closing the association.
SCTP_EOR: This flag, if set and explicit EOR marking (see
Section 8.1.26) is enabled , indicates that the user data
provided is the last part of a user message. If explicit
EOR marking is disabled, this flag is not relevant, since the
user data provided is a complete user message.
SCTP_SENDALL: This flag, if set, will cause a one-to-many
style socket to send the message to all associations that
are currently established on this socket. For the one-to-
one style socket, this flag has no effect.
in Section 5.3.4
SCTP_EOF: Setting this flag invokes the SCTP graceful shutdown
procedures on the specified association. Graceful shutdown
assures that all data queued by both endpoints is successfully
transmitted before closing the association.
SCTP_EOR: This flag, if set and explicit EOR marking (see Section 8.1.26)
is enabled , indicates that the user data provided is the last part of
a user message. If explicit EOR marking is disabled, this flag is
not relevant, since the user data provided is a complete user message.
SCTP_SENDALL: This flag, if set, will cause a one-to-many style
socket to send the message to all associations that are
currently established on this socket. For the one-to-one style
socket, this flag has no effect.
in Section 8.1.13
The sinfo_flags field is composed of a bitwise OR
of SCTP_UNORDERED, SCTP_EOF, SCTP_EOR, and SCTP_SENDALL.
in Section 8.1.31
The snd_flags parameter is composed of a bitwise OR
of SCTP_UNORDERED, SCTP_EOF, SCTP_EOR, and SCTP_SENDALL.
Notes:
The text is missing a description of how to use the SCTP_EOR flag in the Socket API. The problem was initially reported by wanglihe in https://www.rfc-editor.org/errata/eid6081
Errata ID: 6115
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Michael Tuexen
Date Reported: 2020-04-20
Verifier Name: Martin Duke
Date Verified: 2020-04-27
Section 8.2.1 says:
sstat_state: This contains the association's current state, i.e.,
one of the following values:
* SCTP_CLOSED
* SCTP_BOUND
* SCTP_LISTEN
* SCTP_COOKIE_WAIT
* SCTP_COOKIE_ECHOED
* SCTP_ESTABLISHED
* SCTP_SHUTDOWN_PENDING
* SCTP_SHUTDOWN_SENT
* SCTP_SHUTDOWN_RECEIVED
* SCTP_SHUTDOWN_ACK_SENT
It should say:
sstat_state: This contains the association's current state, i.e.,
one of the following values:
* SCTP_CLOSED
* SCTP_LISTEN
* SCTP_COOKIE_WAIT
* SCTP_COOKIE_ECHOED
* SCTP_ESTABLISHED
* SCTP_SHUTDOWN_PENDING
* SCTP_SHUTDOWN_SENT
* SCTP_SHUTDOWN_RECEIVED
* SCTP_SHUTDOWN_ACK_SENT
Notes:
SCTP_BOUND is not a state of an SCTP association, so it should not be part of this list.
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.
Errata ID: 6980
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Michael Tüxen
Date Reported: 2022-05-24
Verifier Name: RFC Editor
Date Verified: 2022-05-24
Section 8 says:
The field opt specifies which SCTP socket option to get. It can get any socket option currently supported that requests information (either read/write options or read-only) such as SCTP_RTOINFO SCTP_ASSOCINFO SCTP_PRIMARY_ADDR SCTP_PEER_ADDR_PARAMS SCTP_DEFAULT_SEND_PARAM SCTP_MAX_SEG SCTP_AUTH_ACTIVE_KEY SCTP_DELAYED_SACK SCTP_MAX_BURST SCTP_CONTEXT SCTP_EVENT SCTP_DEFAULT_SNDINFO SCTP_DEFAULT_PRINFO SCTP_STATUS SCTP_GET_PEER_ADDR_INFO SCTP_PEER_AUTH_CHUNKS SCTP_LOCAL_AUTH_CHUNKS
It should say:
The field opt specifies which SCTP socket option to get. It can get any socket option currently supported that requests information (either read/write options or read-only) such as SCTP_RTOINFO SCTP_ASSOCINFO SCTP_PRIMARY_ADDR SCTP_PEER_ADDR_PARAMS SCTP_DEFAULT_SEND_PARAM SCTP_MAXSEG SCTP_AUTH_ACTIVE_KEY SCTP_DELAYED_SACK SCTP_MAX_BURST SCTP_CONTEXT SCTP_EVENT SCTP_DEFAULT_SNDINFO SCTP_DEFAULT_PRINFO SCTP_STATUS SCTP_GET_PEER_ADDR_INFO SCTP_PEER_AUTH_CHUNKS SCTP_LOCAL_AUTH_CHUNKS
Notes:
The constant SCTP_MAX_SEG is not defined. It should be SCTP_MAXSEG.
Errata ID: 7547
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Michael Tüxen
Date Reported: 2023-06-22
Verifier Name: RFC Editor
Date Verified: 2023-06-22
Section 9.12 says:
info: A pointer to the buffer containing the attribute associated with the message to be sent. The type is indicated by the info_type parameter.
It should say:
info: A pointer to the buffer containing the attribute associated with the message to be sent. The type is indicated by the infotype parameter.
Notes:
The name of the parameter is infotype, not info_type.
Thanks to Philipp Stanner for making me aware of this issue.
Errata ID: 7548
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Michael Tüxen
Date Reported: 2023-06-22
Verifier Name: RFC Editor
Date Verified: 2023-06-22
Section 9.1 says:
info: A pointer to the buffer to hold the attributes of the received
message. The structure type of info is determined by the
info_type parameter.
infolen: An in/out parameter describing the size of the info buffer.
infotype: On return, *info_type is set to the type of the info
buffer. The current defined values are as follows:
SCTP_RECVV_NOINFO: If both SCTP_RECVRCVINFO and SCTP_RECVNXTINFO
options are not enabled, no attribute will be returned. If
only the SCTP_RECVNXTINFO option is enabled but there is no
next message in the buffer, no attribute will be returned. In
these cases, *info_type will be set to SCTP_RECVV_NOINFO.
It should say:
info: A pointer to the buffer to hold the attributes of the received
message. The structure type of info is determined by the
infotype parameter.
infolen: An in/out parameter describing the size of the info buffer.
infotype: On return, *infotype is set to the type of the info
buffer. The current defined values are as follows:
SCTP_RECVV_NOINFO: If both SCTP_RECVRCVINFO and SCTP_RECVNXTINFO
options are not enabled, no attribute will be returned. If
only the SCTP_RECVNXTINFO option is enabled but there is no
next message in the buffer, no attribute will be returned. In
these cases, *infotype will be set to SCTP_RECVV_NOINFO.
Notes:
The name of the parameter is infotype, not info_type.
Thanks to Philipp Stanner for making me aware of this issue.