Javascript disabled? Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.

Zero Checksum for the Stream Control Transmission Protocol
RFC 9653

Revision differences

From revision

To revision

Diff format

Document history

Date	By	Action
2024-09-27	(System)	IANA registries were updated to include RFC9653
2024-09-27	(System)	Received changes through RFC Editor sync (created document RFC 9653, created became rfc relationship between draft-ietf-tsvwg-sctp-zero-checksum and RFC 9653, set abstract to 'The … Received changes through RFC Editor sync (created document RFC 9653, created became rfc relationship between draft-ietf-tsvwg-sctp-zero-checksum and RFC 9653, set abstract to '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.', set pages to 11, set standardization level to Proposed Standard, added RFC published event at 2024-09-27)
2024-09-27	(System)	RFC published

(adsbygoogle = window.adsbygoogle || []).push({});