Skip to main content

Zero Checksum for the Stream Control Transmission Protocol

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Michael Tüxen , Victor Boivie , Florent Castelli , Randell Jesup
Last updated 2023-05-10
Replaced by draft-ietf-tsvwg-sctp-zero-checksum
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tsvwg-sctp-zero-checksum
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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.


Michael Tüxen
Victor Boivie
Florent Castelli
Randell Jesup

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)