A new Request for Comments is now available in online RFC libraries.
RFC 9653
Title: Zero Checksum for the Stream
Control Transmission Protocol
Author: M. Tüxen,
V. Boivie,
F. Castelli,
R. Jesup
Status: Standards Track
Stream: IETF
Date: September 2024
Mailbox: [email protected],
[email protected],
[email protected],
[email protected]
Pages: 11
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tsvwg-sctp-zero-checksum-11.txt
URL: https://www.rfc-editor.org/info/rfc9653
DOI: 10.17487/RFC9653
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.
This document is a product of the Transport and Services Working Group Working
Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
