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
@@ -336636,6 +336638,33 @@ configurations required to deliver them.</p></abstract>
336636
336638
<wg_acronym>bess</wg_acronym>
336637
336639
<doi>10.17487/RFC9856</doi>
336638
336640
</rfc-entry>
336641
+
<rfc-entry>
336642
+
<doc-id>RFC9858</doc-id>
336643
+
<title>Additional Parameter Sets for HSS/LMS Hash-Based Signatures</title>
336644
+
<author>
336645
+
<name>S. Fluhrer</name>
336646
+
</author>
336647
+
<author>
336648
+
<name>Q. Dang</name>
336649
+
</author>
336650
+
<date>
336651
+
<month>October</month>
336652
+
<year>2025</year>
336653
+
</date>
336654
+
<format>
336655
+
<file-format>HTML</file-format>
336656
+
<file-format>TEXT</file-format>
336657
+
<file-format>PDF</file-format>
336658
+
<file-format>XML</file-format>
336659
+
</format>
336660
+
<page-count>25</page-count>
336661
+
<abstract><p>This document extends HSS/LMS (RFC 8554) by defining parameter sets that use alternative hash functions. These include hash functions that result in signatures with significantly smaller sizes than the signatures that use the RFC 8554 parameter sets and should have sufficient security.</p><p> This document is a product of the Internet Research Task Force (IRTF). The IRTF publishes the results of Internet-related research and development activities. These results might not be suitable for deployment. This RFC represents the consensus of the Crypto Forum Research Group of the Internet Research Task Force (IRTF). Documents approved for publication by the IRSG are not candidates for any level of Internet Standard; see Section 2 of RFC 7841.</p></abstract>
@@ -336674,6 +336703,54 @@ configurations required to deliver them.</p></abstract>
336674
336703
<wg_acronym>dnsop</wg_acronym>
336675
336704
<doi>10.17487/RFC9859</doi>
336676
336705
</rfc-entry>
336706
+
<rfc-entry>
336707
+
<doc-id>RFC9861</doc-id>
336708
+
<title>KangarooTwelve and TurboSHAKE</title>
336709
+
<author>
336710
+
<name>B. Viguier</name>
336711
+
</author>
336712
+
<author>
336713
+
<name>D. Wong</name>
336714
+
<title>Editor</title>
336715
+
</author>
336716
+
<author>
336717
+
<name>G. Van Assche</name>
336718
+
<title>Editor</title>
336719
+
</author>
336720
+
<author>
336721
+
<name>Q. Dang</name>
336722
+
<title>Editor</title>
336723
+
</author>
336724
+
<author>
336725
+
<name>J. Daemen</name>
336726
+
<title>Editor</title>
336727
+
</author>
336728
+
<date>
336729
+
<month>October</month>
336730
+
<year>2025</year>
336731
+
</date>
336732
+
<format>
336733
+
<file-format>HTML</file-format>
336734
+
<file-format>TEXT</file-format>
336735
+
<file-format>PDF</file-format>
336736
+
<file-format>XML</file-format>
336737
+
</format>
336738
+
<page-count>28</page-count>
336739
+
<keywords>
336740
+
<kw>Keccak</kw>
336741
+
<kw>Sakura</kw>
336742
+
<kw>KangarooTwelve</kw>
336743
+
<kw>TurboSHAKE</kw>
336744
+
<kw>Cryptographic Hash</kw>
336745
+
<kw>eXtendable Output Function</kw>
336746
+
</keywords>
336747
+
<abstract><p>This document defines four eXtendable-Output Functions (XOFs), hash functions with output of arbitrary length, named TurboSHAKE128, TurboSHAKE256, KT128, and KT256.</p><p> All four functions provide efficient and secure hashing primitives, and the last two are able to exploit the parallelism of the implementation in a scalable way.</p><p> This document is a product of the Crypto Forum Research Group. It builds up on the definitions of the permutations and of the sponge construction in NIST FIPS 202 and is meant to serve as a stable reference and an implementation guide.</p></abstract>
<title>Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) Resources</title>
@@ -336879,6 +336956,38 @@ configurations required to deliver them.</p></abstract>
336879
336956
<wg_acronym>v6ops</wg_acronym>
336880
336957
<doi>10.17487/RFC9872</doi>
336881
336958
</rfc-entry>
336959
+
<rfc-entry>
336960
+
<doc-id>RFC9873</doc-id>
336961
+
<title>Additional Email Address Extension for the Extensible Provisioning Protocol (EPP)</title>
336962
+
<author>
336963
+
<name>D. Belyavsky</name>
336964
+
</author>
336965
+
<author>
336966
+
<name>J. Gould</name>
336967
+
</author>
336968
+
<author>
336969
+
<name>S. Hollenbeck</name>
336970
+
</author>
336971
+
<date>
336972
+
<month>October</month>
336973
+
<year>2025</year>
336974
+
</date>
336975
+
<format>
336976
+
<file-format>HTML</file-format>
336977
+
<file-format>TEXT</file-format>
336978
+
<file-format>PDF</file-format>
336979
+
<file-format>XML</file-format>
336980
+
</format>
336981
+
<page-count>22</page-count>
336982
+
<abstract><p>The Extensible Provisioning Protocol (EPP) does not inherently support internationalized email addresses because the specifications for these addresses did not exist when EPP was developed. This document describes a command-response extension that adds support for associating an additional email address with an EPP contact object. That additional email address can be either an internationalized email address or an ASCII-only address.</p></abstract>
<title>Best Practices for Deletion of Domain and Host Objects in the Extensible Provisioning Protocol (EPP)</title>
@@ -336917,6 +337026,35 @@ configurations required to deliver them.</p></abstract>
336917
337026
<wg_acronym>regext</wg_acronym>
336918
337027
<doi>10.17487/RFC9874</doi>
336919
337028
</rfc-entry>
337029
+
<rfc-entry>
337030
+
<doc-id>RFC9877</doc-id>
337031
+
<title>Registration Data Access Protocol (RDAP) Extension for Geofeed Data</title>
337032
+
<author>
337033
+
<name>J. Singh</name>
337034
+
</author>
337035
+
<author>
337036
+
<name>T. Harrison</name>
337037
+
</author>
337038
+
<date>
337039
+
<month>October</month>
337040
+
<year>2025</year>
337041
+
</date>
337042
+
<format>
337043
+
<file-format>HTML</file-format>
337044
+
<file-format>TEXT</file-format>
337045
+
<file-format>PDF</file-format>
337046
+
<file-format>XML</file-format>
337047
+
</format>
337048
+
<page-count>11</page-count>
337049
+
<abstract><p>This document defines a new Registration Data Access Protocol (RDAP) extension, "geofeed1", for indicating that an RDAP server hosts geofeed URLs for its IP network objects. It also defines a new media type and a new link relation type for the associated link objects included in responses.</p></abstract>
<title>Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax</title>
@@ -336955,6 +337093,35 @@ configurations required to deliver them.</p></abstract>
336955
337093
<wg_acronym>lamps</wg_acronym>
336956
337094
<doi>10.17487/RFC9879</doi>
336957
337095
</rfc-entry>
337096
+
<rfc-entry>
337097
+
<doc-id>RFC9883</doc-id>
337098
+
<title>An Attribute for Statement of Possession of a Private Key</title>
337099
+
<author>
337100
+
<name>R. Housley</name>
337101
+
</author>
337102
+
<date>
337103
+
<month>October</month>
337104
+
<year>2025</year>
337105
+
</date>
337106
+
<format>
337107
+
<file-format>HTML</file-format>
337108
+
<file-format>TEXT</file-format>
337109
+
<file-format>PDF</file-format>
337110
+
<file-format>XML</file-format>
337111
+
</format>
337112
+
<page-count>17</page-count>
337113
+
<keywords>
337114
+
<kw>PKCS#10</kw>
337115
+
</keywords>
337116
+
<abstract><p>This document specifies an attribute for a statement of possession of a private key by a certificate subject. As part of X.509 certificate enrollment, a Certification Authority (CA) typically demands proof that the subject possesses the private key that corresponds to the to-be-certified public key. In some cases, a CA might accept a signed statement from the certificate subject. For example, when a certificate subject needs separate certificates for signature and key establishment, a statement that can be validated with the previously issued signature certificate for the same subject might be adequate for subsequent issuance of the key establishment certificate.</p></abstract>
0 commit comments