RFC 9260, "Stream Control Transmission Protocol", June 2022

Errata ID: 8387
Status: Rejected
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Iñaki Baz Castillo
Date Reported: 2025-04-20
Rejected by: G Fairhurst
Date Rejected: 2026-02-12

Section 3.3.10.6 says:

Unrecognized Chunk: variable length
   The Unrecognized Chunk field contains the unrecognized chunk from
   the SCTP packet complete with Chunk Type, Chunk Flags, and Chunk
   Length.

It should say:

Unrecognized Chunk: variable length
   The Unrecognized Chunk field contains the unrecognized chunk from
   the SCTP packet complete with Chunk Type, Chunk Flags, Chunk Length,
   and Chunk Value.

Notes:

If the Unrecognized Chunk field of the Unrecognized Chunk Type (6) error cause only contained "Chunk Type, Chunk Flags, and Chunk Length" (as the RFC says) then the Cause Length would have fixed value 8. However, Unrecognized Chunk is defined as variable length, meaning that it must contain the entire unrecognized Chunk including its Chunk Value field.
--VERIFIER NOTES--
The suggested text from the reporter would require the sender of the error cause to include the complete chunk with all of its chunk value. It is correct that a chunk consists of a Chunk Type, Chunk Flag, Chunk Length, and Chunk Value. However, requiring a complete chunk value might result in a packet being too large and thus requiring IP level fragmentation. The proposed text was not intended in RFC 9260, and therfore this Erratum is not applied in this form, because the specification cannot be changed.

Report New Errata