[tsvwg] [Errata Verified] RFC6458 (6111)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 27 April 2020 21:54 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 DB5353A0BC7; Mon, 27 Apr 2020 14:54:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1jc32PBsr4zJ; Mon, 27 Apr 2020 14:54:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60D623A0BDA; Mon, 27 Apr 2020 14:54:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 87CA2F4072C; Mon, 27 Apr 2020 14:54:11 -0700 (PDT)
To: tuexen@fh-muenster.de, randall@lakerest.net, tuexen@fh-muenster.de, ka-cheong.poon@oracle.com, peterlei@cisco.com, vladislav.yasevich@hp.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: martin.h.duke@gmail.com, iesg@ietf.org, tsvwg@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200427215411.87CA2F4072C@rfc-editor.org>
Date: Mon, 27 Apr 2020 14:54:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/TmW9h5dF44X3-9i7NfYBCflPkfE>
Subject: [tsvwg] [Errata Verified] RFC6458 (6111)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 27 Apr 2020 21:54:26 -0000
The following errata report has been verified 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/eid6111 -------------------------------------- Status: Verified Type: Technical Reported by: Michael Tuexen <tuexen@fh-muenster.de> Date Reported: 2020-04-20 Verified by: Martin Duke (IESG) Section: GLOBAL Original Text ------------- 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. Corrected Text -------------- 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 -------------------------------------- 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] [Errata Verified] RFC6458 (6111) RFC Errata System