[tsvwg] [Errata Verified] RFC9260 (7852)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 18 March 2025 08:01 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id CB99ADA07C8; Tue, 18 Mar 2025 01:01:23 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 8F3621D56DD; Tue, 18 Mar 2025 01:01:23 -0700 (PDT)
To: tuexen@freebsd.org, randall@lakerest.net, tuexen@fh-muenster.de, kee@kamstrup.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20250318080123.8F3621D56DD@rfcpa.rfc-editor.org>
Date: Tue, 18 Mar 2025 01:01:23 -0700
Message-ID-Hash: K6MMXNT3K2BW6ZJRZ2FGGPEIYHJZY6LT
X-Message-ID-Hash: K6MMXNT3K2BW6ZJRZ2FGGPEIYHJZY6LT
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tsvwg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: zaheduzzaman.sarker@nokia.com, iesg@ietf.org, tsvwg@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [tsvwg] [Errata Verified] RFC9260 (7852)
List-Id: Transport Area Working Group <tsvwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/PEJN6FIArOohFIjoHIIykqMudpk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Owner: <mailto:tsvwg-owner@ietf.org>
List-Post: <mailto:tsvwg@ietf.org>
List-Subscribe: <mailto:tsvwg-join@ietf.org>
List-Unsubscribe: <mailto:tsvwg-leave@ietf.org>

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

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

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Michael Tüxen <tuexen@freebsd.org>
Date Reported: 2024-03-15
Verified by: Zaheduzzaman Sarker (IESG)

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.

--------------------------------------
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