[tsvwg] [Editorial Errata Reported] RFC6458 (6112)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 20 April 2020 13:48 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 A506C3A0D77 for <tsvwg@ietfa.amsl.com>; Mon, 20 Apr 2020 06:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[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 DXUxbSnGUtTV for <tsvwg@ietfa.amsl.com>; Mon, 20 Apr 2020 06:48:58 -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 1495B3A0D80 for <tsvwg@ietf.org>; Mon, 20 Apr 2020 06:48:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1543AF406CD; Mon, 20 Apr 2020 06:48:55 -0700 (PDT)
To: randall@lakerest.net, tuexen@fh-muenster.de, ka-cheong.poon@oracle.com, peterlei@cisco.com, vladislav.yasevich@hp.com, martin.h.duke@gmail.com, magnus.westerlund@ericsson.com, david.black@dell.com, gorry@erg.abdn.ac.uk, wes@mti-systems.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: tuexen@fh-muenster.de, tsvwg@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20200420134855.1543AF406CD@rfc-editor.org>
Date: Mon, 20 Apr 2020 06:48:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/5EUDxpovAgujC5tjuE12GyyPCyk>
Subject: [tsvwg] [Editorial Errata Reported] RFC6458 (6112)
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, 20 Apr 2020 13:49:00 -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/eid6112 -------------------------------------- Type: Editorial Reported by: Michael Tuexen <tuexen@fh-muenster.de> Section: 3.2 Original Text ------------- 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. Corrected Text -------------- 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. 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 (6112) RFC Errata System