RFC 6458, "Sockets API Extensions for the Stream Control Transmission Protocol (SCTP)", December 2011

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.

Report New Errata