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

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Tue, 19 March 2024 16:45 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 40CFEC14F68C for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2024 09:45:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 3ku8290xenWK for <tsvwg@ietfa.amsl.com>; Tue, 19 Mar 2024 09:45:52 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 56786C14F5E9 for <tsvwg@ietf.org>; Tue, 19 Mar 2024 09:45:50 -0700 (PDT)
Received: from [192.168.1.130] (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 6044E1B0020F; Tue, 19 Mar 2024 16:45:40 +0000 (GMT)
Message-ID: <47f514a4-4ae6-4cc2-817a-0b19afa9cfc7@erg.abdn.ac.uk>
Date: Tue, 19 Mar 2024 16:45:39 +0000
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-GB
To: Randall Stewart <randall@lakerest.net>, Rebecca VanRheenen <rvanrheenen@amsl.com>, Martin Duke <martin.h.duke@gmail.com>
Cc: tuexen@fh-muenster.de, tuexen@freebsd.org, tsvwg@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
References: <20240315164733.7A22176350@rfcpa.amsl.com> <F8BF9AFB-238A-4419-94CA-F01A81A7C0E2@amsl.com> <e95a41db-1ff4-4e1f-a07a-7f94948e7db2@lakerest.net>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: UNIVERSITY OF ABERDEEN
In-Reply-To: <e95a41db-1ff4-4e1f-a07a-7f94948e7db2@lakerest.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/E5LcSg48rbZPacbC5zI1U3CfeR8>
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:45:56 -0000

On 19/03/2024 16:33, Randall Stewart wrote:
> 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

I concur - I always understood that the V-Tag ought to be first checked 
before continuing further processing.

Best wishes,

Gorry

(TSVWG Co-Chaor)

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