You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -327746,6 +327749,41 @@ been incorporated into this document. This document obsoletes RFC
327746
327749
<wg_acronym>lsr</wg_acronym>
327747
327750
<doi>10.17487/RFC9650</doi>
327748
327751
</rfc-entry>
327752
+
<rfc-entry>
327753
+
<doc-id>RFC9653</doc-id>
327754
+
<title>Zero Checksum for the Stream Control Transmission Protocol</title>
327755
+
<author>
327756
+
<name>M. Tüxen</name>
327757
+
</author>
327758
+
<author>
327759
+
<name>V. Boivie</name>
327760
+
</author>
327761
+
<author>
327762
+
<name>F. Castelli</name>
327763
+
</author>
327764
+
<author>
327765
+
<name>R. Jesup</name>
327766
+
</author>
327767
+
<date>
327768
+
<month>September</month>
327769
+
<year>2024</year>
327770
+
</date>
327771
+
<format>
327772
+
<file-format>HTML</file-format>
327773
+
<file-format>TEXT</file-format>
327774
+
<file-format>PDF</file-format>
327775
+
<file-format>XML</file-format>
327776
+
</format>
327777
+
<page-count>11</page-count>
327778
+
<abstract><p>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.</p><p> 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.</p></abstract>
<title>Online Certificate Status Protocol (OCSP) Nonce Extension</title>
@@ -327779,6 +327817,79 @@ been incorporated into this document. This document obsoletes RFC
327779
327817
<wg_acronym>lamps</wg_acronym>
327780
327818
<doi>10.17487/RFC9654</doi>
327781
327819
</rfc-entry>
327820
+
<rfc-entry>
327821
+
<doc-id>RFC9659</doc-id>
327822
+
<title>Window Sizing for Zstandard Content Encoding</title>
327823
+
<author>
327824
+
<name>N. Jaju</name>
327825
+
<title>Editor</title>
327826
+
</author>
327827
+
<author>
327828
+
<name>W. F. Handte</name>
327829
+
<title>Editor</title>
327830
+
</author>
327831
+
<date>
327832
+
<month>September</month>
327833
+
<year>2024</year>
327834
+
</date>
327835
+
<format>
327836
+
<file-format>HTML</file-format>
327837
+
<file-format>TEXT</file-format>
327838
+
<file-format>PDF</file-format>
327839
+
<file-format>XML</file-format>
327840
+
</format>
327841
+
<page-count>4</page-count>
327842
+
<keywords>
327843
+
<kw>zstd</kw>
327844
+
<kw>zstandard</kw>
327845
+
<kw>compression</kw>
327846
+
<kw>content encoding</kw>
327847
+
<kw>content coding</kw>
327848
+
<kw>application/zstd</kw>
327849
+
</keywords>
327850
+
<abstract><p>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.</p></abstract>
<title>The JSON Meta Application Protocol (JMAP) for Sieve Scripts</title>
327865
+
<author>
327866
+
<name>K. Murchison</name>
327867
+
</author>
327868
+
<date>
327869
+
<month>September</month>
327870
+
<year>2024</year>
327871
+
</date>
327872
+
<format>
327873
+
<file-format>HTML</file-format>
327874
+
<file-format>TEXT</file-format>
327875
+
<file-format>PDF</file-format>
327876
+
<file-format>XML</file-format>
327877
+
</format>
327878
+
<page-count>21</page-count>
327879
+
<keywords>
327880
+
<kw>JMAP</kw>
327881
+
<kw>JSON</kw>
327882
+
<kw>Sieve</kw>
327883
+
</keywords>
327884
+
<abstract><p>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.</p></abstract>
0 commit comments