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

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 06 October 2022 09:56 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 C2A52C14CF00 for <tsvwg@ietfa.amsl.com>; Thu, 6 Oct 2022 02:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.661
X-Spam-Level:
X-Spam-Status: No, score=-0.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 udyrmg6tLhri for <tsvwg@ietfa.amsl.com>; Thu, 6 Oct 2022 02:56:44 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [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 00EA8C14F73E for <tsvwg@ietf.org>; Thu, 6 Oct 2022 02:56:43 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id BABEC55ECA; Thu, 6 Oct 2022 02:56:43 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: tuexen@fh-muenster.de, randall@lakerest.net, tuexen@fh-muenster.de, kee@kamstrup.com, tsvwg@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20221006095643.BABEC55ECA@rfcpa.amsl.com>
Date: Thu, 06 Oct 2022 02:56:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/cz2ipNJiMnsqb7dIOj9BTYwZv_g>
Subject: [tsvwg] [Editorial Errata Reported] RFC9260 (7147)
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: Thu, 06 Oct 2022 09:56:47 -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/eid7147

--------------------------------------
Type: Editorial
Reported by: Michael Tüxen <tuexen@fh-muenster.de>

Section: 3.2

Original Text
-------------
          +----+--------------------------------------------------+
          | 00 | Stop processing this SCTP packet and discard the |
          |    | unrecognized chunk and all further chunks.       |
          +----+--------------------------------------------------+
          | 01 | Stop processing this SCTP packet, discard the    |
          |    | unrecognized chunk and all further chunks, and   |
          |    | report the unrecognized chunk in an ERROR chunk  |
          |    | using the 'Unrecognized Chunk Type' error cause. |
          +----+--------------------------------------------------+
          | 10 | Skip this chunk and continue processing.         |
          +----+--------------------------------------------------+
          | 11 | Skip this chunk and continue processing, but     |
          |    | report it in an ERROR chunk using the            |
          |    | 'Unrecognized Chunk Type' error cause.           |
          +----+--------------------------------------------------+


Corrected Text
--------------
          +----+--------------------------------------------------+
          | 00 | Stop processing this SCTP packet and discard the |
          |    | unrecognized chunk and all further chunks.       |
          +----+--------------------------------------------------+
          | 01 | Stop processing this SCTP packet, discard the    |
          |    | unrecognized chunk and all further chunks, and   |
          |    | report the unrecognized chunk in an ERROR chunk  |
          |    | using the "Unrecognized Chunk Type" error cause. |
          +----+--------------------------------------------------+
          | 10 | Skip this chunk and continue processing.         |
          +----+--------------------------------------------------+
          | 11 | Skip this chunk and continue processing, but     |
          |    | report it in an ERROR chunk using the            |
          |    | "Unrecognized Chunk Type" error cause.           |
          +----+--------------------------------------------------+


Notes
-----
In the rest of the document, error cause names are enclosed in double quotes, not in single quotes.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can 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 Area Working Group
Area                : Transport
Stream              : IETF
Verifying Party     : IESG