{
  "draft": "draft-ietf-tsvwg-sctp-zero-checksum-11",
  "doc_id": "RFC9653",
  "title": "Zero Checksum for the Stream Control Transmission Protocol",
  "authors": [
    "M. T\u00fcxen",
    "V. Boivie",
    "F. Castelli",
    "R. Jesup"
  ],
  "format": [
    "XML",
    "TEXT",
    "HTML",
    "PDF"
  ],
  "page_count": "11",
  "pub_status": "PROPOSED STANDARD",
  "status": "PROPOSED STANDARD",
  "source": "Transport and Services Working Group",
  "abstract": "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.\n\n 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.",
  "pub_date": "September 2024",
  "keywords": [],
  "obsoletes": [],
  "obsoleted_by": [],
  "updates": [],
  "updated_by": [],
  "see_also": [],
  "doi": "10.17487/RFC9653",
  "errata_url": null
}