<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.tuexen-tsvwg-sctp-zero-checksum" target="https://datatracker.ietf.org/doc/html/draft-tuexen-tsvwg-sctp-zero-checksum-03">
   <front>
      <title>Zero Checksum for the Stream Control Transmission Protocol</title>
      <author initials="M." surname="Tüxen" fullname="Michael Tüxen">
         <organization>Münster University of Applied Sciences</organization>
      </author>
      <author initials="V." surname="Boivie" fullname="Victor Boivie">
         <organization>Google</organization>
      </author>
      <author initials="F." surname="Castelli" fullname="Florent Castelli">
         <organization>Google</organization>
      </author>
      <author initials="R." surname="Jesup" fullname="Randell Jesup">
         <organization>Mozilla Corporation</organization>
      </author>
      <date month="May" day="10" year="2023" />
      <abstract>
	 <t>   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.  When the lower layer used by SCTP provides already
   the same or a higher level of data integrity, computing this checksum
   does not provide any additional protection, but does require
   computing resources.  This document provides a simple extension to
   SCTP allowing to save these computing resources by using the constant
   0 as the checksum in a backwards compatible way.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-tuexen-tsvwg-sctp-zero-checksum-03" />
   
</reference>
