-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
github-actions
committed
Sep 28, 2024
1 parent
56db9bf
commit 9d95f98
Showing
4 changed files
with
71 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
<reference anchor="RFC.9653" target="https://www.rfc-editor.org/info/rfc9653"> | ||
<front> | ||
<title>Zero Checksum for the Stream Control Transmission Protocol</title> | ||
<author fullname="M. Tüxen" initials="M." surname="Tüxen"> | ||
<organization/> | ||
</author> | ||
<author fullname="V. Boivie" initials="V." surname="Boivie"> | ||
<organization/> | ||
</author> | ||
<author fullname="F. Castelli" initials="F." surname="Castelli"> | ||
<organization/> | ||
</author> | ||
<author fullname="R. Jesup" initials="R." surname="Jesup"> | ||
<organization/> | ||
</author> | ||
<author> | ||
<organization>RFC Series</organization> | ||
</author> | ||
<date year="2024" month="September"/> | ||
<workgroup>tsvwg</workgroup> | ||
<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. 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.</t> | ||
<t>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.</t> | ||
</abstract> | ||
</front> | ||
<seriesInfo name="DOI" value="10.17487/RFC9653"/> | ||
<seriesInfo name="RFC" value="9653"/> | ||
<seriesInfo name="IETF"/> | ||
</reference> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
<reference anchor="RFC.9659" target="https://www.rfc-editor.org/info/rfc9659"> | ||
<front> | ||
<title>Window Sizing for Zstandard Content Encoding</title> | ||
<author role="editor" fullname="N. Jaju" initials="N." surname="Jaju"> | ||
<organization/> | ||
</author> | ||
<author role="editor" fullname="W. F. Handte" initials="W. F." surname="Handte"> | ||
<organization/> | ||
</author> | ||
<author> | ||
<organization>RFC Series</organization> | ||
</author> | ||
<date year="2024" month="September"/> | ||
<workgroup>httpbis</workgroup> | ||
<abstract> | ||
<t>Deployments of Zstandard, or "zstd", can use different window sizes to limit memory usage during compression and decompression. Some browsers and user agents limit window sizes to mitigate memory usage concerns, thereby causing interoperability issues. This document updates the window size limit in RFC 8878 from a recommendation to a requirement in HTTP contexts.</t> | ||
</abstract> | ||
</front> | ||
<seriesInfo name="DOI" value="10.17487/RFC9659"/> | ||
<seriesInfo name="RFC" value="9659"/> | ||
<seriesInfo name="IETF"/> | ||
</reference> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
<reference anchor="RFC.9661" target="https://www.rfc-editor.org/info/rfc9661"> | ||
<front> | ||
<title>The JSON Meta Application Protocol (JMAP) for Sieve Scripts</title> | ||
<author fullname="K. Murchison" initials="K." surname="Murchison"> | ||
<organization/> | ||
</author> | ||
<author> | ||
<organization>RFC Series</organization> | ||
</author> | ||
<date year="2024" month="September"/> | ||
<workgroup>jmap</workgroup> | ||
<abstract> | ||
<t>This document specifies a data model for managing Sieve scripts on a server using the JSON Meta Application Protocol (JMAP). Clients can use this protocol to efficiently search, access, organize, and validate Sieve scripts.</t> | ||
</abstract> | ||
</front> | ||
<seriesInfo name="DOI" value="10.17487/RFC9661"/> | ||
<seriesInfo name="RFC" value="9661"/> | ||
<seriesInfo name="IETF"/> | ||
</reference> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
Fri Sep 27 15:17:21 UTC 2024 | ||
Sat Sep 28 15:17:36 UTC 2024 |