[tsvwg] Adoption call fordraft-tuexen-tsvwg-sctp-zero-checksum - to conclude 25th April 2023

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Tue, 11 April 2023 08:31 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 29ABFC151532 for <tsvwg@ietfa.amsl.com>; Tue, 11 Apr 2023 01:31:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Status: No, score=-6.899 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] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id VgRME-vqq74j for <tsvwg@ietfa.amsl.com>; Tue, 11 Apr 2023 01:31:48 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk []) by ietfa.amsl.com (Postfix) with ESMTP id 86510C14CE27 for <tsvwg@ietf.org>; Tue, 11 Apr 2023 01:31:47 -0700 (PDT)
Received: from [] (fgrpf.plus.com []) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 57D531B001B7 for <tsvwg@ietf.org>; Tue, 11 Apr 2023 09:31:43 +0100 (BST)
Message-ID: <e9c1cb50-64cb-3d13-2c57-ffb15a101059@erg.abdn.ac.uk>
Date: Tue, 11 Apr 2023 09:31:42 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.9.0
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/cDUBDfJ2fGNtnySHwrn6AQvu8V4>
Subject: [tsvwg] Adoption call fordraft-tuexen-tsvwg-sctp-zero-checksum - to conclude 25th April 2023
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, 11 Apr 2023 08:31:54 -0000

This email now marks the start of a WG adoption call for: Zero Checksum 
for the Stream Control Transmission Protocol 
(draft-tuexen-tsvwg-sctp-zero-checksum-02). This draft was discussed at 
the recent TSVWG meeting.


    The Stream Control Transmission Protocol (SCTP) uses a 32-bit
    checksum in the common header of each packet to provide some level of
    data integrity.  When the lower layer used by SCTP provides already
    the same or a higher level of data integrity, computing this checksum
    does not provide any additional protection, but does require
    computing resources.  This document provides a simple extension to
    SCTP allowing to save these computing resources by using the constant
    0 as the checksum in a backwards compatible way.

Please read this draft, and send any comments/concerns to either the 
TSVWG or to the chairs <tsvwg-chairs@ietf.org>.  Notes of support to 
progress this work, and volunteers to review the drafts will also be 
very welcome at this stage.

All participants, should disclose any relevant intellectual property 
rights (IPR) under [RFC8179].

Best wishes,
Gorry and Marten
(tsvwg co-chairs)