[tsvwg] [Editorial Errata Reported] RFC9260 (7852)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 15 March 2024 16:47 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 8CF3BC14F699 for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2024 09:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.657
X-Spam-Level:
X-Spam-Status: No, score=-6.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 IHVEEdQO-6Qc for <tsvwg@ietfa.amsl.com>; Fri, 15 Mar 2024 09:47:33 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 B781BC14F616 for <tsvwg@ietf.org>; Fri, 15 Mar 2024 09:47:33 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 7A22176350; Fri, 15 Mar 2024 09:47:33 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: tuexen@freebsd.org, randall@lakerest.net, tuexen@fh-muenster.de, kee@kamstrup.com, tsvwg@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240315164733.7A22176350@rfcpa.amsl.com>
Date: Fri, 15 Mar 2024 09:47:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/DfjjAv_QZ7TsMilxzfH5f1QJGd0>
Subject: [tsvwg] [Editorial Errata Reported] RFC9260 (7852)
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: Fri, 15 Mar 2024 16:47:37 -0000

The following errata report has been submitted for RFC9260,
"Stream Control Transmission Protocol".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7852

--------------------------------------
Type: Editorial
Reported by: Michael Tüxen <tuexen@freebsd.org>

Section: 8.5.

Original Text
-------------
When receiving an SCTP packet, the endpoint MUST ensure that the
value in the Verification Tag field of the received SCTP packet
matches its own tag.

Corrected Text
--------------
When receiving an SCTP packet, the endpoint MUST first ensure that the
value in the Verification Tag field of the received SCTP packet
matches its own tag before processing any chunks or changing its state.

Notes
-----
State explicitly that the check of the verification tag needs to be done before any processing of the packet.

Thanks to Jake Ginesin, Max von Hippel, and Cristina Nita-Rotaru for reporting issue and discussing it with me.

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
will log in to change the status and edit the report, if necessary.

--------------------------------------
RFC9260 (draft-ietf-tsvwg-rfc4960-bis-19)
--------------------------------------
Title               : Stream Control Transmission Protocol
Publication Date    : June 2022
Author(s)           : R. Stewart, M. Tüxen, K. Nielsen
Category            : PROPOSED STANDARD
Source              : Transport and Services Working Group
Stream              : IETF
Verifying Party     : IESG