[tsvwg] [Editorial Errata Reported] RFC6458 (7548)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 22 June 2023 20:45 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E766C15108E for <tsvwg@ietfa.amsl.com>; Thu, 22 Jun 2023 13:45:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.808
X-Spam-Level:
X-Spam-Status: No, score=-5.808 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.84, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hTehJdoSJhdW for <tsvwg@ietfa.amsl.com>; Thu, 22 Jun 2023 13:45:19 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A776FC14CEED for <tsvwg@ietf.org>; Thu, 22 Jun 2023 13:45:19 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 867338528B; Thu, 22 Jun 2023 13:45:19 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: tuexen@fh-muenster.de, randall@lakerest.net, tuexen@fh-muenster.de, ka-cheong.poon@oracle.com, peterlei@cisco.com, vladislav.yasevich@hp.com, tsvwg@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230622204519.867338528B@rfcpa.amsl.com>
Date: Thu, 22 Jun 2023 13:45:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/mfhTNRSw3_rOI8DTv7M8IYbycCM>
Subject: [tsvwg] [Editorial Errata Reported] RFC6458 (7548)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jun 2023 20:45:23 -0000
The following errata report has been submitted for RFC6458, "Sockets API Extensions for the Stream Control Transmission Protocol (SCTP)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7548 -------------------------------------- Type: Editorial Reported by: Michael Tüxen <tuexen@fh-muenster.de> Section: 9.13 Original Text ------------- 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. Corrected Text -------------- 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. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC6458 (draft-ietf-tsvwg-sctpsocket-32) -------------------------------------- Title : Sockets API Extensions for the Stream Control Transmission Protocol (SCTP) Publication Date : December 2011 Author(s) : R. Stewart, M. Tuexen, K. Poon, P. Lei, V. Yasevich Category : INFORMATIONAL Source : Transport Area Working Group Area : Transport Stream : IETF Verifying Party : IESG
- [tsvwg] [Editorial Errata Reported] RFC6458 (7548) RFC Errata System