RFC 3309: Stream Control Transmission Protocol (SCTP) Checksum Change
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4960.
Current document in this lineage: RFC 9260 — Stream Control Transmission Protocol
In plain English — editorial summary, not part of the RFC
Stream Control Transmission Protocol [RFC2960] (SCTP) currently uses an Adler-32 checksum. For small packets Adler-32 provides weak detection of errors. This document changes that checksum and updates SCTP to use a 32 bit CRC checksum.
Document record
- Document ID
- RFC3309
- Published
- September 2002
- Authors
- J. Stone; R. Stewart; D. Otis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 17
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 8 RFCs, each formally replacing the one before it.
- RFC 2960 (2000)
- RFC 3309 (2002)
- RFC 4460 (2006)
- RFC 4960 (2007)
- RFC 6096 (2011)
- RFC 7053 (2013)
- RFC 8540 (2019)
- RFC 9260 (2022) ✓
Read the full history of Stream Control Transmission Protocol →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7510Encapsulating MPLS in UDPCurrent
April 2015
- RFC 7820UDP Checksum Complement in the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)Current
March 2016
- RFC 7821UDP Checksum Complement in the Network Time Protocol (NTP)Updated
March 2016
- RFC 8976Message Digest for DNS ZonesCurrent
February 2021
- RFC 3390Increasing TCP's Initial WindowCurrent
November 2002
- RFC 3436Transport Layer Security over Stream Control Transmission ProtocolUpdated
December 2002
- RFC 3448TCP Friendly Rate Control (TFRC): Protocol SpecificationObsoleted
January 2003
- RFC 3168The Addition of Explicit Congestion Notification (ECN) to IPUpdated
September 2001
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?