metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9653: Zero Checksum for the Stream Control Transmission Protocol

In plain English — editorial summary, not part of the RFC

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. If another method used by SCTP already provides the same or a higher level of data integrity, computing this checksum does not provide any additional protection but does consume computing resources. This document provides a simple extension allowing SCTP to save these computing resources by using zero as the checksum in a backwards-compatible way. It also defines how this feature can be used when SCTP packets are encapsulated in Datagram Transport Layer Security (DTLS) packets.

Document record

Document ID
RFC9653
Published
September 2024
Authors
M. Tüxen; V. Boivie; F. Castelli; R. Jesup
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
11
Also known as
—

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9653-zero-checksum-for-the-stream-control-transmission-protocol