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

Randall Stewart <randall@lakerest.net> Tue, 19 March 2024 16:33 UTC

Return-Path: <randall@lakerest.net>
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 CC8BEC14CEFC for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2024 09:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ZN398wKgE8AH for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2024 09:33:35 -0700 (PDT)
Received: from smtp-out.a.misk.com (smtp-out.a.misk.com [199.47.128.30]) (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 E9A0BC14F747 for <tsvwg@ietf.org>; Tue, 19 Mar 2024 09:33:34 -0700 (PDT)
X-Authenticated-User: randall@lakerest.net
Received: from 10.1.2.133 (072-239-139-254.res.spectrum.com [72.239.139.254]) by smtp.misk.com (MiskSMTP) with ESMTPSA id 1db1f6e4c94c4d2bae7dd8ca13cc6734 for <tsvwg@ietf.org>; Tue, 19 Mar 2024 16:33:23 +0000
Message-ID: <e95a41db-1ff4-4e1f-a07a-7f94948e7db2@lakerest.net>
Date: Tue, 19 Mar 2024 12:33:22 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: Rebecca VanRheenen <rvanrheenen@amsl.com>, Martin Duke <martin.h.duke@gmail.com>
Cc: tuexen@freebsd.org, tuexen@fh-muenster.de, kee@kamstrup.com, tsvwg@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
References: <20240315164733.7A22176350@rfcpa.amsl.com> <F8BF9AFB-238A-4419-94CA-F01A81A7C0E2@amsl.com>
From: Randall Stewart <randall@lakerest.net>
In-Reply-To: <F8BF9AFB-238A-4419-94CA-F01A81A7C0E2@amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/7Snj150PwJLBu97IppVOkxPNBmY>
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:33:38 -0000

Rebecca:


I do think this is an editorial change. It was always intended that you 
*always* verify the V-Tag *before* you

do anything else. So this is just a clarification in the spec IMO.


Best wishes

Randall Stewart

On 3/19/24 12:26 PM, Rebecca VanRheenen wrote:
> Hi Martin,
>
> We are unable to verify this erratum that the submitter marked as editorial, so we changed the Type to “Technical”. 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:
> https://www.rfc-editor.org/errata/eid7852
>
> Information on how to verify errata reports can be found at:
> https://www.rfc-editor.org/how-to-verify/
>
> Further information on errata can be found at:
> 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:
>>
>> 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
>>