From rvanrheenen@amsl.com  Tue Mar 19 09:26:29 2024
Return-Path: <rvanrheenen@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 BFD11C14CF12
 for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2024 09:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level: 
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3,
 RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001,
 T_SCC_BODY_TEXT_LINE=-0.01, 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 f3y0tbk6lXyz for <tsvwg@ietfa.amsl.com>;
 Tue, 19 Mar 2024 09:26:26 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40])
 (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 07DF1C14F70E
 for <tsvwg@ietf.org>; Tue, 19 Mar 2024 09:26:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
 by c8a.amsl.com (Postfix) with ESMTP id 9AE92424B427;
 Tue, 19 Mar 2024 09:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1])
 by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 3oiRfFvim3Ta; Tue, 19 Mar 2024 09:26:25 -0700 (PDT)
Received: from [IPv6:2601:641:300:5fb0:498a:472a:af0b:f3e9] (unknown
 [IPv6:2601:641:300:5fb0:498a:472a:af0b:f3e9])
 by c8a.amsl.com (Postfix) with ESMTPSA id 76AC9424B426;
 Tue, 19 Mar 2024 09:26:25 -0700 (PDT)
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Rebecca VanRheenen <rvanrheenen@amsl.com>
In-Reply-To: <20240315164733.7A22176350@rfcpa.amsl.com>
Date: Tue, 19 Mar 2024 09:26:24 -0700
Cc: tuexen@freebsd.org, randall@lakerest.net, tuexen@fh-muenster.de,
 kee@kamstrup.com, tsvwg@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8BF9AFB-238A-4419-94CA-F01A81A7C0E2@amsl.com>
References: <20240315164733.7A22176350@rfcpa.amsl.com>
To: Martin Duke <martin.h.duke@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/sBz4jaJP5xuKhCsqGTADi_JqSmo>
Subject: Re: [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: Tue, 19 Mar 2024 16:26:29 -0000

Hi Martin,

We are unable to verify this erratum that the submitter marked as =
editorial, so we changed the Type to =E2=80=9CTechnical=E2=80=9D. As =
Stream Approver, please review and set the Status and Type accordingly =
(see the definitions at https://www.rfc-editor.org/errata-definitions/).

You may review the report at:=20
https://www.rfc-editor.org/errata/eid7852

Information on how to verify errata reports can be found at:=20
https://www.rfc-editor.org/how-to-verify/

Further information on errata can be found at:=20
https://www.rfc-editor.org/errata.php

Thank you.

RFC Editor/rv


> On Mar 15, 2024, at 9:47 AM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC9260,
> "Stream Control Transmission Protocol".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7852
>=20
> --------------------------------------
> Type: Editorial
> Reported by: Michael T=C3=BCxen <tuexen@freebsd.org>
>=20
> Section: 8.5.
>=20
> 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.
>=20
> 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.
>=20
> Notes
> -----
> State explicitly that the check of the verification tag needs to be =
done before any processing of the packet.
>=20
> Thanks to Jake Ginesin, Max von Hippel, and Cristina Nita-Rotaru for =
reporting issue and discussing it with me.
>=20
> Instructions:
> -------------
> This erratum is currently posted as "Reported". (If it is spam, it=20
> 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 =20
> will log in to change the status and edit the report, if necessary.
>=20
> --------------------------------------
> RFC9260 (draft-ietf-tsvwg-rfc4960-bis-19)
> --------------------------------------
> Title               : Stream Control Transmission Protocol
> Publication Date    : June 2022
> Author(s)           : R. Stewart, M. T=C3=BCxen, K. Nielsen
> Category            : PROPOSED STANDARD
> Source              : Transport and Services Working Group
> Stream              : IETF
> Verifying Party     : IESG
>=20

