Approving on my side too! On Tue, Sep 30, 2025 at 12:22 PM Alanna Paloma <[email protected]> wrote: > > Hi Gilles and Quynh, > > Thank you for your replies. Your approvals have been noted on the AUTH48 > status page: > https://www.rfc-editor.org/auth48/rfc9861 > > Best regards, > Alanna Paloma > RFC Production Center > > > On Sep 30, 2025, at 3:42 AM, Dang, Quynh H. (Fed) <[email protected]> > > wrote: > > > > Hi Alanna Paloma, > > > > Thank you for all the good edits you made. > > > > I approve them. > > > > Regards, > > Quynh. > > > >> -----Original Message----- > >> From: Gilles VAN ASSCHE <[email protected]> > >> Sent: Tuesday, September 30, 2025 5:11 AM > >> To: Alanna Paloma <[email protected]>; > >> [email protected]; Joan Daemen <[email protected]> > >> Cc: [email protected]; [email protected]; Dang, Quynh H. (Fed) > >> <[email protected]>; RFC Editor <[email protected]>; > >> [email protected]; > >> auth48archive <[email protected]> > >> Subject: [EXTERNAL] RE: [Document Shepherd] Re: AUTH48: RFC-to-be 9861 > >> <draft-irtf-cfrg-kangarootwelve-17> for your review > >> > >> Dear Alanna Paloma, > >> > >> I reviewed the latest version of the document and hereby approve it. > >> > >> Kind regards, > >> Gilles > >> > >> -----Original Message----- > >> From: Alanna Paloma <[email protected]> > >> Sent: mercredi 24 septembre 2025 00:51 > >> To: [email protected]; Joan Daemen <[email protected]>; Gilles > >> VAN ASSCHE <[email protected]> > >> Cc: [email protected]; [email protected]; [email protected]; > >> RFC Editor <[email protected]>; [email protected]; auth48archive > >> <[email protected]> > >> Subject: [Document Shepherd] Re: AUTH48: RFC-to-be 9861 <draft-irtf-cfrg- > >> kangarootwelve-17> for your review > >> > >> Hi Authors and Nick*, > >> > >> *Nick - As the Document Shepherd, please review and approve of this added > >> sentence at the end of Section 1. > >> > >> Old: > >> This document represents the consensus of the Crypto Forum Research > >> Group (CFRG) in the IRTF. It is not an IETF product and is not a > >> standard. > >> > >> Current: > >> This document represents the consensus of the Crypto Forum Research > >> Group (CFRG) in the IRTF. It has been reviewed by two members of the > >> Crypto Review Panel, as well as by several members of the CFRG. It > >> is not an IETF product and is not a standard. > >> > >> See this diff file: > >> > >> https://www/. > >> rfc-editor.org%2Fauthors%2Frfc9861- > >> auth48diff.html&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b6 > >> 7bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec%7 > >> C0%7C0%7C638948203290022772%7CUnknown%7CTWFpbGZsb3d8eyJFb > >> XB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTW > >> FpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ehTWzc4LaX3slacklGvJY > >> T6zZY03IPMBT%2FhCASZkGbY%3D&reserved=0 > >> > >> > >> Gilles and Joan - Thank you for your replies. We have updated the files > >> per > >> your response in the submitted XML file. > >> > >> The files have been posted here (please refresh): > >> > >> https://www/. > >> rfc- > >> editor.org%2Fauthors%2Frfc9861.xml&data=05%7C02%7Cquynh.dang%40ni > >> st.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a > >> 93e054655c61dec%7C0%7C0%7C638948203290041551%7CUnknown%7C > >> TWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJ > >> XaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=x > >> xjjCMMIt9tXqs7sY8i4CJJZ5tzXYQnaJAPmESK4Tf0%3D&reserved=0 > >> > >> https://www/. > >> rfc- > >> editor.org%2Fauthors%2Frfc9861.txt&data=05%7C02%7Cquynh.dang%40ni > >> st.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a > >> 93e054655c61dec%7C0%7C0%7C638948203290054431%7CUnknown%7C > >> TWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJ > >> XaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=R > >> wrVZBjmsl3MoilVMXyqTGEPHvZ20GtmYRBhhI6yLLo%3D&reserved=0 > >> > >> https://www/. > >> rfc- > >> editor.org%2Fauthors%2Frfc9861.html&data=05%7C02%7Cquynh.dang%40 > >> nist.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797 > >> a93e054655c61dec%7C0%7C0%7C638948203290067248%7CUnknown%7 > >> CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOi > >> JXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata= > >> zuLfVRyKeOcZmfsht%2F7OumqxtAqRpFE4ef%2F0ISQQkJo%3D&reserved=0 > >> > >> https://www/. > >> rfc- > >> editor.org%2Fauthors%2Frfc9861.pdf&data=05%7C02%7Cquynh.dang%40ni > >> st.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a > >> 93e054655c61dec%7C0%7C0%7C638948203290079800%7CUnknown%7C > >> TWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJ > >> XaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=C > >> gV8sO1eK5Wcmv9L1YPiCaiNb3lXgAtmjb%2BmfOsXgAI%3D&reserved=0 > >> > >> The relevant diff files have been posted here: > >> > >> https://www/. > >> rfc-editor.org%2Fauthors%2Frfc9861- > >> diff.html&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b67bc43c > >> 95b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec%7C0%7C > >> 0%7C638948203290093739%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU > >> 1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIs > >> IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=DSf1fqX%2BTLFR%2Bg7Sec9e > >> C0QnZYVWz9K2pwv1%2FcyVYUI%3D&reserved=0 (comprehensive diff) > >> https://www/. > >> rfc-editor.org%2Fauthors%2Frfc9861- > >> auth48diff.html&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b6 > >> 7bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec%7 > >> C0%7C0%7C638948203290107198%7CUnknown%7CTWFpbGZsb3d8eyJFb > >> XB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTW > >> FpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=VBBld3tethf3WYVsQm > >> AXxzAwLP6y4sMeDBX0fuzmRLQ%3D&reserved=0 (AUTH48 changes) > >> https://www/. > >> rfc-editor.org%2Fauthors%2Frfc9861- > >> auth48rfcdiff.html&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19 > >> b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec > >> %7C0%7C0%7C638948203290119632%7CUnknown%7CTWFpbGZsb3d8ey > >> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi > >> TWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=o1WN8J2AKli4KOb9 > >> MUHUu1ggSMOSRfHaeFVf0iHWe18%3D&reserved=0 (AUTH48 changes side > >> by side) > >> > >> Please review the document carefully and contact us with any further > >> updates > >> you may have. Note that we do not make changes once a document is > >> published as an RFC. > >> > >> We will await any further changes you may have and approvals from each > >> author and *Nick prior to moving forward in the publication process. > >> > >> For the AUTH48 status of this document, please see: > >> > >> https://www/. > >> rfc- > >> editor.org%2Fauth48%2Frfc9861&data=05%7C02%7Cquynh.dang%40nist.g > >> ov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e > >> 054655c61dec%7C0%7C0%7C638948203290132258%7CUnknown%7CTW > >> FpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXa > >> W4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=f31 > >> Q4CbkEd5AE79js%2BFIFBUOYu5k0Fx17WAU72bV%2FZY%3D&reserved=0 > >> > >> Thank you, > >> Alanna Paloma > >> RFC Production Center > >> > >>> On Sep 23, 2025, at 2:41 AM, Joan Daemen <[email protected]> wrote: > >>> > >>> Dear Alanna Paloma, > >>> > >>> On 23/09/2025 11:24, Gilles VAN ASSCHE wrote: > >>>> Dear Alanna Paloma, > >>>> > >>>> Sorry for the delay. > >>>> > >>>> Please find enclosed answers to your comments and questions. From > >>>> informal discussions with the other authors, I know that some of them > >>>> agree with these, but I let them confirm officially. :-) > >>> > >>> I agree with all of them. > >>> > >>> Kind regards, > >>> > >>> Joan > >>> > >>>> > >>>> Kind regards, > >>>> Gilles > >>>> > >>>> > >>>> ST Restricted > >>>> -----Original Message----- > >>>> From: Alanna Paloma <[email protected]> > >>>> Sent: lundi 22 septembre 2025 19:56 > >>>> To: [email protected]; [email protected]; Gilles VAN > >>>> ASSCHE <[email protected]>; [email protected]; [email protected] > >>>> Cc: RFC Editor <[email protected]>; [email protected]; > >>>> [email protected]; auth48archive > >>>> <[email protected]> > >>>> Subject: Re: AUTH48: RFC-to-be 9861 > >>>> <draft-irtf-cfrg-kangarootwelve-17> for your review > >>>> > >>>> Greetings, > >>>> > >>>> We do not believe we have heard from you regarding this document's > >> readiness for publication. Please review our previous messages describing > >> the > >> AUTH48 process and containing any document-specific questions we may > >> have had. > >>>> > >>>> We will wait to hear from you before continuing with the publication > >> process. > >>>> > >>>> The AUTH48 status page for this document is located here: > >>>> > >> https://www/ > >>>> .rfc- > >> editor.org%2Fauth48%2Frfc9861&data=05%7C02%7Cquynh.dang%40nist.g > >>>> > >> ov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e > >> 054655c61 > >>>> > >> dec%7C0%7C0%7C638948203290144712%7CUnknown%7CTWFpbGZsb3d > >> 8eyJFbXB0eU1h > >>>> > >> cGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld > >> UI > >>>> > >> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=swN%2FUERPRzB0tCzvClBoevgSi9x > >> 88Mqe1qNy > >>>> t1fOHnY%3D&reserved=0 > >>>> > >>>> Thank you, > >>>> Alanna Paloma > >>>> RFC Production Center > >>>> > >>>>> On Sep 15, 2025, at 6:20 PM, [email protected] wrote: > >>>>> > >>>>> Authors, > >>>>> > >>>>> While reviewing this document during AUTH48, please resolve (as > >> necessary) the following questions, which are also in the source file. > >>>>> > >>>>> 1) <!--[rfced] Please ensure that the guidelines listed in Section > >>>>> 2.1 of RFC 5743 have been adhered to in this document. --> > >>>>> > >>>>> > >>>>> 2) <!--[rfced] Should the document's short title, which can be seen > >>>>> in the header of the PDF output, include "TurboSHAKE" to reflect the > >>>>> full > >> document title? > >>>>> > >>>>> Original: > >>>>> KangarooTwelve > >>>>> > >>>>> Perhaps: > >>>>> KangarooTwelve and TurboSHAKE > >>>>> --> > >>>>> > >>>>> > >>>>> 3) <!--[rfced] May we clarify that "similarly to the SHAKE's" is > >>>>> referring to the SHAKE's security? > >>>>> > >>>>> Original: > >>>>> Similarly to the SHAKE's, it proposes two security strengths: > >>>>> 128 bits for TurboSHAKE128 and 256 bits for TurboSHAKE256. > >>>>> > >>>>> Perhaps: > >>>>> Similarly to the SHAKE's security, it proposes two security strengths: > >>>>> 128 bits for TurboSHAKE128 and 256 bits for TurboSHAKE256. > >>>>> --> > >>>>> > >>>>> > >>>>> 4) <!--[rfced] Section 1. We rephrased the following sentence for > >>>>> consistency with the other sentences in the list and to avoid using > >>>>> citations as adjectives. If it changes the intended meaning, please > >>>>> let us know. > >>>>> > >>>>> Original: > >>>>> * Unlike any [FIPS202] and [SP800-185] functions but ParallelHash, > >>>>> KT128 and KT256 exploit available parallelism. > >>>>> > >>>>> Perhaps: > >>>>> * Unlike any functions in [FIPS202] and [SP800-185] except for > >>>>> ParallelHash, KT128 and KT256 exploit available parallelism. > >>>>> --> > >>>>> > >>>>> > >>>>> 5) <!--[rfced] Section 2.1. We rephrased this text to match similar > >>>>> text in the first paragraph of Section 3.1. If it changes the > >>>>> intended meaning, please let us know. > >>>>> > >>>>> Original: > >>>>> An instance of TurboSHAKE takes as input parameters a byte-string M, > >>>>> an OPTIONAL byte D and a positive integer L where > >>>>> > >>>>> Current: > >>>>> A TurboSHAKE instance takes a byte string M, an OPTIONAL byte D, and > >>>>> a positive integer L as input parameters, where: > >>>>> --> > >>>>> > >>>>> > >>>>> 6) <!--[rfced] Please clarify "for any distinct values D1 and D2". > >>>>> Is the current text correct or is the intended meaning "for distinct > >>>>> values D1 and D2" (i.e., without "any")? > >>>>> > >>>>> Original: > >>>>> Specifically, for any distinct values D1 and D2, TurboSHAKE(M, D1, > >>>>> L1) and TurboSHAKE(M, D2, L2) yield independent hashes of M. > >>>>> > >>>>> Perhaps: > >>>>> Specifically, for distinct values D1 and D2, TurboSHAKE(M, D1, > >>>>> L1) and TurboSHAKE(M, D2, L2) yield independent hashes of M. > >>>>> --> > >>>>> > >>>>> > >>>>> 7) <!--[rfced] Is the space before the colon in "l_e( x ) :" > >>>>> intentional, or may we update the text as follows to avoid the added > >> space? > >>>>> > >>>>> Current: > >>>>> The following figure illustrates the computation flow of KT128 > >>>>> for |S| > 8192 bytes and where TurboSHAKE128 and length_encode( x ) > >>>>> are abbreviated respectively as TSHK128 and l_e( x ) : > >>>>> > >>>>> Perhaps: > >>>>> The following figure illustrates the computation flow of KT128 > >>>>> for |S| > 8192 bytes and where TurboSHAKE128 and length_encode( x ) > >>>>> are abbreviated as TSHK128 and l_e( x ), respectively: > >>>>> --> > >>>>> > >>>>> > >>>>> 8) <!--[rfced] In the "COSE Algorithms" registry at > >>>>> > >> <https://w/ > >>>>> > >> ww.iana.org%2Fassignments%2Fcose&data=05%7C02%7Cquynh.dang%40ni > >> st.go > >>>>> > >> v%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e0 > >> 54655c61dec%7C0%7C0%7C638948203290157258%7CUnknown%7CTWF > >> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW > >> 4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=gXey9 > >> 77FP29WSWzFD8N0niQhqIwpvdyEkYfBc72oPRo%3D&reserved=0>, IANA > >> lists the values in descending order. Should Table 3 be ordered to match > >> the > >> IANA registry (e.g., list "KT256 | -264 " first and "TurboSHAKE128 | -261" > >> last)? > >>>>> > >>>>> Also, may we include the "Recommended" column in Table 3 to match > >>>>> the IANA registry or include the following sentence in the lead-in text? > >>>>> Please let us know which option is preferred. > >>>>> > >>>>> Current: > >>>>> In the COSE Algorithms "COSE Algorithms" registry, IANA has added > >>>>> the following entries for TurboSHAKE and KangarooTwelve: > >>>>> > >>>>> Perhaps: > >>>>> In the COSE Algorithms "COSE Algorithms" registry, IANA has added > >>>>> the following entries for TurboSHAKE and KangarooTwelve. For each > >>>>> entry, the "Recommended" column contains "No". > >>>>> --> > >>>>> > >>>>> > >>>>> 9) <!--[rfced] To improve the readability of "the output L MUST be > >>>>> chosen long enough", may we update it to "the chose L output MUST be > >> long enough"? > >>>>> Note that this phrasing occurs in two sentences. > >>>>> > >>>>> Original: > >>>>> To achieve 128-bit > >>>>> security strength, the output L MUST be chosen long enough so that > >>>>> there are no generic attacks that violate 128-bit security. > >>>>> ... > >>>>> To achieve 256-bit security strength, the output L MUST be chosen long > >>>>> enough so that there are no generic attacks that violate 256-bit > >>>>> security. > >>>>> > >>>>> Perhaps: > >>>>> To achieve 128-bit > >>>>> security strength, the chosen L output MUST be long enough so that > >>>>> there are no generic attacks that violate 128-bit security. > >>>>> ... > >>>>> To achieve 256-bit security strength, the chosen L output MUST be long > >>>>> enough so that there are no generic attacks that violate 256-bit > >>>>> security. > >>>>> --> > >>>>> > >>>>> > >>>>> 10) <!--[rfced] As the first sentence is not a full sentence, may we > >>>>> combine the two sentences below into one sentence? > >>>>> > >>>>> Original: > >>>>> Lastly, as KT128 and KT256 use TurboSHAKE with three values for D, > >>>>> namely 0x06, 0x07, and 0x0B. Protocols that use both KT128 and > >>>>> TurboSHAKE128, or both KT256 and TurboSHAKE256, SHOULD avoid > >> using > >>>>> these three values for D. > >>>>> > >>>>> Perhaps: > >>>>> Lastly, as KT128 and KT256 use TurboSHAKE with three values for D, > >>>>> namely 0x06, 0x07, and 0x0B, protocols that use both KT128 and > >>>>> TurboSHAKE128 or both KT256 and TurboSHAKE256 SHOULD avoid > >> using > >>>>> these three values for D. > >>>>> --> > >>>>> > >>>>> > >>>>> 11) <!-- [rfced] References > >>>>> > >>>>> a) Would you like the references to be alphabetized or left in their > >>>>> current order? > >>>>> > >>>>> > >>>>> b) We note that the original [KT] reference entry contained two URL > >>>>> strings. > >>>>> > >>>>> The first URL is to a pre-print version of this article available > >>>>> from the Cryptology ePrint Archive with the most recent version > >>>>> being added in May 2018: > >> http://eprint/. > >> iacr.org%2F2016%2F770.pdf&data=05%7C02%7Cquynh.dang%40nist.gov% > >> 7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e0546 > >> 55c61dec%7C0%7C0%7C638948203290169671%7CUnknown%7CTWFpbG > >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zM > >> iIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=orahu8Yw > >> F1hwCFITSDzgZWj34GlBVorRdSydXhXNzAY%3D&reserved=0. > >>>>> > >>>>> The other URL is to the published conference paper with a date of > >>>>> June > >>>>> 2018: > >> https://link.s/ > >> pringer.com%2Fchapter%2F10.1007%2F978-3-319-93387- > >> 0_21&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b67bc43c95 > >> b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec%7C0%7C0% > >> 7C638948203290181994%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc > >> GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld > >> UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=031MTyog0F%2BC6Pc%2FFAjLG > >> LR70KoHvscXbn1tB2wEQ34%3D&reserved=0. > >>>>> > >>>>> We have modified this reference to use the Springer Link URL as this > >>>>> appears to be the most recently published version that also includes > >>>>> a DOI. Please review and let us know if you have any objections. > >>>>> > >>>>> Original: > >>>>> [KT] Bertoni, G., Daemen, J., Peeters, M., Van Assche, G., Van > >>>>> Keer, R., and B. Viguier, "KangarooTwelve: fast hashing > >>>>> based on Keccak-p", WWW > >> https://link.s/ > >> pringer.com%2F&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b > >> 67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec% > >> 7C0%7C0%7C638948203290194463%7CUnknown%7CTWFpbGZsb3d8eyJF > >> bXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiT > >> WFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=6guFBKvft8RZQzqCE9 > >> cAaS9WU%2B3CkJYlSz9ZfHvA0i8%3D&reserved=0 > >>>>> chapter/10.1007/978-3-319-93387-0_21, > >>>>> WWW > >> http://eprint/. > >> iacr.org%2F2016%2F770.pdf&data=05%7C02%7Cquynh.dang%40nist.gov% > >> 7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e0546 > >> 55c61dec%7C0%7C0%7C638948203290206791%7CUnknown%7CTWFpbG > >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zM > >> iIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PVCAuXdJ > >> 4wFO%2BIh92b0tTtki867HjyyRt7Jchxjj2hY%3D&reserved=0, July 2018. > >>>>> > >>>>> Current: > >>>>> [KT] Bertoni, G., Daemen, J., Peeters, M., Van Assche, G., Van > >>>>> Keer, R., and B. Viguier, "KangarooTwelve: Fast Hashing > >>>>> Based on Keccak-p", Applied Cryptography and Network > >>>>> Security (ACNS 2018), Lecture Notes in Computer Science, > >>>>> vol. 10892, pp. 400-418, DOI 10.1007/978-3-319-93387-0_21, > >>>>> June 2018, > >> <https://link/. > >> springer.com%2F&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b > >> 67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec% > >> 7C0%7C0%7C638948203290219060%7CUnknown%7CTWFpbGZsb3d8eyJF > >> bXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiT > >> WFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=hTI5Ih%2BWHG7h8t > >> O1JTpHFAtecO6OX2k5bqIEohyGZ3o%3D&reserved=0 > >>>>> chapter/10.1007/978-3-319-93387-0_21>. > >>>>> > >>>>> > >>>>> c) We note that the original [SAKURA] reference entry contained two > >>>>> URL strings. > >>>>> > >>>>> The first URL is to a pre-print version of this article available > >>>>> from the Cryptology ePrint Archive with the most recent version > >>>>> being added in April 2014: > >> https://eprint/ > >> .iacr.org%2F2013%2F231.pdf&data=05%7C02%7Cquynh.dang%40nist.gov% > >> 7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e0546 > >> 55c61dec%7C0%7C0%7C638948203290231422%7CUnknown%7CTWFpbG > >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zM > >> iIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=kx0sb2ZC > >> gruceAiXHJMT8yvdocKG3qCMDbpI%2FUX%2FrHQ%3D&reserved=0. > >>>>> > >>>>> The other URL is to the published conference paper with a date of > >>>>> 2014: > >> https://link.s/ > >> pringer.com%2Fchapter%2F10.1007%2F978-3-319-07536- > >> 5_14&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b67bc43c95 > >> b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec%7C0%7C0% > >> 7C638948203290243950%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hc > >> GkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIld > >> UIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=tz7V5LxzgAYCxUKT5TrV1%2B%2 > >> BiuYnylK4GRGstj35QVco%3D&reserved=0. > >>>>> > >>>>> We have modified this reference to use the Springer Link URL as this > >>>>> appears to be the most recently published version that also includes > >>>>> a DOI. Please review and let us know if you have any objections. > >>>>> > >>>>> Original: > >>>>> [SAKURA] Bertoni, G., Daemen, J., Peeters, M., and G. Van Assche, > >>>>> "Sakura: a flexible coding for tree hashing", WWW > >>>>> > >> https://link.s/ > >> pringer.com%2F&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b > >> 67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec% > >> 7C0%7C0%7C638948203290258943%7CUnknown%7CTWFpbGZsb3d8eyJF > >> bXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiT > >> WFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=aP14nNEVvjMN1O6 > >> GFse7w2QeO%2Fc7b11BGp4WadsaVVI%3D&reserved=0 > >>>>> chapter/10.1007/978-3-319-07536-5_14, > >>>>> WWW > >> http://eprint/. > >> iacr.org%2F2013%2F231.pdf&data=05%7C02%7Cquynh.dang%40nist.gov% > >> 7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e0546 > >> 55c61dec%7C0%7C0%7C638948203290271394%7CUnknown%7CTWFpbG > >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zM > >> iIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=grMdklEK > >> Z5SFonDltrdjI9eLGh0Bc0jILRNwV%2Fb1yG8%3D&reserved=0, June 2014. > >>>>> > >>>>> Current: > >>>>> [SAKURA] Bertoni, G., Daemen, J., Peeters, M., and G. Van Assche, > >>>>> "Sakura: a Flexible Coding for Tree Hashing", Applied > >>>>> Cryptography and Network Security (ACNS 2014), Lecture > >>>>> Notes in Computer Science, vol. 8479, pp. 217-234, > >>>>> DOI 10.1007/978-3-319-07536-5_14, 2014, > >>>>> > >> <https://link/. > >> springer.com%2F&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b > >> 67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec% > >> 7C0%7C0%7C638948203290283706%7CUnknown%7CTWFpbGZsb3d8eyJF > >> bXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiT > >> WFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=cbP%2BbDLkEBmARs > >> cqQMfSe0hCaWBC4ITHd2GGtb7nwjM%3D&reserved=0 > >>>>> chapter/10.1007/978-3-319-07536-5_14>. > >>>>> > >>>>> > >>>>> d) Since this reference is to a GitHub repository, please provide a > >>>>> commit hash in accordance with Part 2 of the RFC Style > >>>>> Guide: > >> https://www/. > >> rfc- > >> editor.org%2Fstyleguide%2Fpart2%2F%23ref_repo&data=05%7C02%7Cquy > >> nh.dang%40nist.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d > >> 82fd8fa4797a93e054655c61dec%7C0%7C0%7C638948203290296326%7C > >> Unknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMD > >> AwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7 > >> C%7C&sdata=HTcnhyeuiD1jEOM5sRnxvGTI4ivb0wsCXW6tpktWINE%3D&res > >> erved=0. > >>>>> > >>>>> [XKCP] "eXtended Keccak Code Package", December 2022, > >>>>> > >> <https://gith/ > >> ub.com%2FXKCP%2FXKCP&data=05%7C02%7Cquynh.dang%40nist.gov%7C > >> 28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e054655 > >> c61dec%7C0%7C0%7C638948203290309315%7CUnknown%7CTWFpbGZs > >> b3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs > >> IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=me6GaZeGd > >> aQzh8QQ%2Bi7PtVkPzinxR%2BRkhTLn3SGGoX8%3D&reserved=0>. > >>>>> --> > >>>>> > >>>>> > >>>>> 12) <!--[rfced] The following lines are 1 character over the > >>>>> 72-character limit. Please let us know how you would like to adjust > >>>>> the lines/spacing. > >>>>> > >>>>> Appendix A.4: > >>>>> CV = TurboSHAKE128(S[offset : offset + blockSize], `0B`, 32) > >>>>> > >>>>> Appendix A.5: > >>>>> CV = TurboSHAKE256(S[offset : offset + blockSize], `0B`, 64) > >>>>> --> > >>>>> > >>>>> > >>>>> 13) <!--[rfced] Throughout the text, the following terminology > >>>>> appears to be used inconsistently. Please review these occurrences > >>>>> and let us know if/how they may be made consistent. > >>>>> > >>>>> Chaining Value vs. chaining value > >>>>> Customization string vs. customization string Message vs. message > >>>>> --> > >>>>> > >>>>> > >>>>> 14) <!-- [rfced] Abbreviations > >>>>> > >>>>> a) FYI - We have added expansions for the following abbreviations > >>>>> per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review each > >>>>> expansion in the document carefully to ensure correctness. > >>>>> > >>>>> Elliptic Curve Diffie-Hellman (ECDH) Hashed Message Authentication > >>>>> Code (HMAC) Original Dialog Identifier > >>>>> (ODI) single instruction, multiple data (SIMD) > >>>>> > >>>>> b) FYI: We added a hyphen to the expansion of "XOF" per [FIPS202] > >>>>> and the NIST glossary. > >>>>> > >>>>> eXtendable Output Functions -> eXtendable-Output Functions > >>>>> --> > >>>>> > >>>>> > >>>>> 15) <!-- [rfced] Please review the "Inclusive Language" portion of > >>>>> the online Style Guide > >>>>> > >> <https://w/ > >>>>> ww.rfc- > >> editor.org%2Fstyleguide%2Fpart2%2F%23inclusive_language&data= > >>>>> > >> 05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b67bc43c95b1708de000 > >> 160d9%7 > >>>>> > >> C2ab5d82fd8fa4797a93e054655c61dec%7C0%7C0%7C638948203290321 > >> 935%7CUnk > >>>>> > >> nown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAw > >> MCIsIlAiO > >>>>> > >> iJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata= > >> oxPKH > >>>>> > >> HUViFhK6DGNKHpLSk%2Fe7rZzt2mX%2BRtsM%2Bfi2rQ%3D&reserved=0> > >>>>> and let us know if any changes are needed. > >>>>> > >>>>> Note that our script did not flag any words in particular, but this > >>>>> should still be reviewed as a best practice. > >>>>> --> > >>>>> > >>>>> > >>>>> Thank you. > >>>>> > >>>>> Alanna Paloma and Karen Moore > >>>>> RFC Production Center > >>>>> > >>>>> > >>>>> > >>>>> On Sep 15, 2025, at 6:17 PM, RFC Editor via auth48archive > >> <[email protected]> wrote: > >>>>> > >>>>> *****IMPORTANT***** > >>>>> > >>>>> Updated 2025/09/15 > >>>>> > >>>>> RFC Author(s): > >>>>> -------------- > >>>>> > >>>>> Instructions for Completing AUTH48 > >>>>> > >>>>> Your document has now entered AUTH48. Once it has been reviewed and > >>>>> approved by you and all coauthors, it will be published as an RFC. > >>>>> If an author is no longer available, there are several remedies > >>>>> available as listed in the FAQ > >> (https://ww/ > >> w.rfc- > >> editor.org%2Ffaq%2F&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0 > >> f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61d > >> ec%7C0%7C0%7C638948203290334459%7CUnknown%7CTWFpbGZsb3d8 > >> eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI > >> joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Md7hwoiY1u64A > >> lmiuQeHeLJG3BWSP7nBUHzQEVcAZI4%3D&reserved=0). > >>>>> > >>>>> You and you coauthors are responsible for engaging other parties > >>>>> (e.g., Contributors or Working Group) as necessary before providing > >>>>> your approval. > >>>>> > >>>>> Planning your review > >>>>> --------------------- > >>>>> > >>>>> Please review the following aspects of your document: > >>>>> > >>>>> * RFC Editor questions > >>>>> > >>>>> Please review and resolve any questions raised by the RFC Editor > >>>>> that have been included in the XML file as comments marked as > >>>>> follows: > >>>>> > >>>>> <!-- [rfced] ... --> > >>>>> > >>>>> These questions will also be sent in a subsequent email. > >>>>> > >>>>> * Changes submitted by coauthors > >>>>> > >>>>> Please ensure that you review any changes submitted by your > >>>>> coauthors. We assume that if you do not speak up that you agree to > >>>>> changes submitted by your coauthors. > >>>>> > >>>>> * Content > >>>>> > >>>>> Please review the full content of the document, as this cannot > >>>>> change once the RFC is published. Please pay particular attention to: > >>>>> - IANA considerations updates (if applicable) > >>>>> - contact information > >>>>> - references > >>>>> > >>>>> * Copyright notices and legends > >>>>> > >>>>> Please review the copyright notice and legends as defined in RFC > >>>>> 5378 and the Trust Legal Provisions (TLP – > >>>>> > >> https://truste/ > >> e.ietf.org%2Flicense- > >> info&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b67bc43c95b > >> 1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec%7C0%7C0%7 > >> C638948203290346958%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcG > >> kiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUI > >> joyfQ%3D%3D%7C0%7C%7C%7C&sdata=W7QsYWSRoqwkiRWWVfnrnZIewv > >> nUu79Hstzt853uVQ8%3D&reserved=0). > >>>>> > >>>>> * Semantic markup > >>>>> > >>>>> Please review the markup in the XML file to ensure that elements of > >>>>> content are correctly tagged. For example, ensure that <sourcecode> > >>>>> and <artwork> are set correctly. See details at > >>>>> > >> <https://auth/ > >> ors.ietf.org%2Frfcxml- > >> vocabulary&data=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b67bc4 > >> 3c95b1708de000160d9%7C2ab5d82fd8fa4797a93e054655c61dec%7C0%7 > >> C0%7C638948203290359203%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0e > >> U1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbC > >> IsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Vz0vH1GD%2BAqsA1URwvC > >> cUMwzFLQyPJtErMq9VgB3hpA%3D&reserved=0>. > >>>>> > >>>>> * Formatted output > >>>>> > >>>>> Please review the PDF, HTML, and TXT files to ensure that the > >>>>> formatted output, as generated from the markup in the XML file, is > >>>>> reasonable. Please note that the TXT will have formatting > >>>>> limitations compared to the PDF and HTML. > >>>>> > >>>>> > >>>>> Submitting changes > >>>>> ------------------ > >>>>> > >>>>> To submit changes, please reply to this email using ‘REPLY ALL’ as > >>>>> all the parties CCed on this message need to see your changes. The > >>>>> parties > >>>>> include: > >>>>> > >>>>> * your coauthors > >>>>> > >>>>> * [email protected] (the RPC team) > >>>>> > >>>>> * other document participants, depending on the stream (e.g., > >>>>> IETF Stream participants are your working group chairs, the > >>>>> responsible ADs, and the document shepherd). > >>>>> > >>>>> * [email protected], which is a new archival mailing list > >>>>> to preserve AUTH48 conversations; it is not an active discussion > >>>>> list: > >>>>> > >>>>> * More info: > >>>>> > >>>>> > >> https://ma/ > >>>>> ilarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh- > >> 4Q9l2US&d > >>>>> > >> ata=05%7C02%7Cquynh.dang%40nist.gov%7C28a0f19b67bc43c95b1708de > >> 000160 > >>>>> > >> d9%7C2ab5d82fd8fa4797a93e054655c61dec%7C0%7C0%7C63894820329 > >> 0371572%7 > >>>>> > >> CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuM > >> DAwMCIsI > >>>>> > >> lAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sd > >> ata=F > >>>>> dB8JYo6Lt%2FyiqYekA5MMytisxWqszgpyiQlqQGrXVE%3D&reserved=0 > >>>>> xI > >>>>> Ae6P8O4Zc > >>>>> > >>>>> * The archive itself: > >>>>> > >>>>> > >> https://ma/ > >>>>> > >> ilarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C02% > >> 7 > >>>>> > >> Cquynh.dang%40nist.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2 > >> ab5d82f > >>>>> > >> d8fa4797a93e054655c61dec%7C0%7C0%7C638948203290384004%7CUn > >> known%7CTW > >>>>> > >> FpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXa > >> W4zMi > >>>>> > >> IsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=K%2FlwR0 > >> YRsuYy > >>>>> 58TC6IP3qIOX6tnreZ3JrX4LgV7jLgo%3D&reserved=0 > >>>>> > >>>>> * Note: If only absolutely necessary, you may temporarily opt out > >>>>> of the archiving of messages (e.g., to discuss a sensitive matter). > >>>>> If needed, please add a note at the top of the message that you > >>>>> have dropped the address. When the discussion is concluded, > >>>>> [email protected] will be re-added to the CC list and > >>>>> its addition will be noted at the top of the message. > >>>>> > >>>>> You may submit your changes in one of two ways: > >>>>> > >>>>> An update to the provided XML file > >>>>> — OR — > >>>>> An explicit list of changes in this format > >>>>> > >>>>> Section # (or indicate Global) > >>>>> > >>>>> OLD: > >>>>> old text > >>>>> > >>>>> NEW: > >>>>> new text > >>>>> > >>>>> You do not need to reply with both an updated XML file and an > >>>>> explicit list of changes, as either form is sufficient. > >>>>> > >>>>> We will ask a stream manager to review and approve any changes that > >>>>> seem beyond editorial in nature, e.g., addition of new text, > >>>>> deletion of text, and technical changes. Information about stream > >>>>> managers can be found in the FAQ. Editorial changes do not require > >> approval from a stream manager. > >>>>> > >>>>> > >>>>> Approving for publication > >>>>> -------------------------- > >>>>> > >>>>> To approve your RFC for publication, please reply to this email > >>>>> stating that you approve this RFC for publication. Please use > >>>>> ‘REPLY ALL’, as all the parties CCed on this message need to see your > >> approval. > >>>>> > >>>>> > >>>>> Files > >>>>> ----- > >>>>> > >>>>> The files are available here: > >>>>> > >>>>> > >> https://ww/ > >>>>> w.rfc- > >> editor.org%2Fauthors%2Frfc9861.xml&data=05%7C02%7Cquynh.dang%4 > >>>>> > >> 0nist.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa479 > >> 7a93e0 > >>>>> > >> 54655c61dec%7C0%7C0%7C638948203290396524%7CUnknown%7CTWF > >> pbGZsb3d8eyJ > >>>>> > >> FbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi > >> TWF > >>>>> > >> pbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PqwqRqP91MBUJf9TuO > >> bMkXlH7Tw > >>>>> q2y0yx1ShC9rvEyw%3D&reserved=0 > >>>>> > >>>>> > >> https://ww/ > >>>>> w.rfc- > >> editor.org%2Fauthors%2Frfc9861.html&data=05%7C02%7Cquynh.dang% > >>>>> > >> 40nist.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa47 > >> 97a93e > >>>>> > >> 054655c61dec%7C0%7C0%7C638948203290409478%7CUnknown%7CTW > >> FpbGZsb3d8ey > >>>>> > >> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi > >> TW > >>>>> > >> FpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=8%2BgTsDlDlOg41N5DL > >> ZW%2BEW > >>>>> w5V0MBrXbOqFRYj068PPY%3D&reserved=0 > >>>>> > >>>>> > >> https://ww/ > >>>>> w.rfc- > >> editor.org%2Fauthors%2Frfc9861.pdf&data=05%7C02%7Cquynh.dang%4 > >>>>> > >> 0nist.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa479 > >> 7a93e0 > >>>>> > >> 54655c61dec%7C0%7C0%7C638948203290421772%7CUnknown%7CTWF > >> pbGZsb3d8eyJ > >>>>> > >> FbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi > >> TWF > >>>>> > >> pbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=i%2FhRPoW6toMQwvjfz > >> 2iZZwurf > >>>>> KsulctRnVT0J1kAukM%3D&reserved=0 > >>>>> > >>>>> > >> https://ww/ > >>>>> w.rfc- > >> editor.org%2Fauthors%2Frfc9861.txt&data=05%7C02%7Cquynh.dang%4 > >>>>> > >> 0nist.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa479 > >> 7a93e0 > >>>>> > >> 54655c61dec%7C0%7C0%7C638948203290434411%7CUnknown%7CTWF > >> pbGZsb3d8eyJ > >>>>> > >> FbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi > >> TWF > >>>>> > >> pbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=cUbIlIKnMDCAf4tCAbU > >> DB5FW6oX > >>>>> L7c%2BLuMlx%2F0tuG9I%3D&reserved=0 > >>>>> > >>>>> Diff file of the text: > >>>>> > >>>>> > >> https://ww/ > >>>>> w.rfc-editor.org%2Fauthors%2Frfc9861- > >> diff.html&data=05%7C02%7Cquynh. > >>>>> > >> dang%40nist.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82f > >> d8fa479 > >>>>> > >> 7a93e054655c61dec%7C0%7C0%7C638948203290446945%7CUnknown% > >> 7CTWFpbGZsb > >>>>> > >> 3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsI > >> kFOI > >>>>> > >> joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=YDUwIMsHWc5Jq > >> X1%2Bbpl > >>>>> bWGRn5PJoudOZHwVp0qcpCgk%3D&reserved=0 > >>>>> > >>>>> > >> https://ww/ > >>>>> w.rfc-editor.org%2Fauthors%2Frfc9861- > >> rfcdiff.html&data=05%7C02%7Cquy > >>>>> > >> nh.dang%40nist.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d > >> 82fd8fa > >>>>> > >> 4797a93e054655c61dec%7C0%7C0%7C638948203290459169%7CUnkno > >> wn%7CTWFpbG > >>>>> > >> Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zM > >> iIsIk > >>>>> > >> FOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Vh6N3kmjMf > >> v2FqGpey > >>>>> hIkKgDKpqYd1j20iydPvnj7bU%3D&reserved=0 (side by > >>>>> side) > >>>>> > >>>>> Diff of the XML: > >>>>> > >>>>> > >> https://ww/ > >>>>> w.rfc-editor.org%2Fauthors%2Frfc9861- > >> xmldiff1.html&data=05%7C02%7Cqu > >>>>> > >> ynh.dang%40nist.gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5 > >> d82fd8f > >>>>> > >> a4797a93e054655c61dec%7C0%7C0%7C638948203290471444%7CUnkno > >> wn%7CTWFpb > >>>>> > >> GZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4z > >> MiIsI > >>>>> > >> kFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ksRIAGDagyh > >> SLv2tA > >>>>> bzOJYYtpa9biaoB1fbOcto2uJE%3D&reserved=0 > >>>>> > >>>>> > >>>>> Tracking progress > >>>>> ----------------- > >>>>> > >>>>> The details of the AUTH48 status of your document are here: > >>>>> > >>>>> > >> https://ww/ > >>>>> w.rfc- > >> editor.org%2Fauth48%2Frfc9861&data=05%7C02%7Cquynh.dang%40nist > >>>>> > >> .gov%7C28a0f19b67bc43c95b1708de000160d9%7C2ab5d82fd8fa4797a93 > >> e054655 > >>>>> > >> c61dec%7C0%7C0%7C638948203290483973%7CUnknown%7CTWFpbGZs > >> b3d8eyJFbXB0 > >>>>> > >> eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpb > >> CIs > >>>>> > >> IldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=lFuY10h2XpMxU7Oazdey%2F > >> 90X8AlE6j > >>>>> iN0qP74wKkRFY%3D&reserved=0 > >>>>> > >>>>> Please let us know if you have any questions. > >>>>> > >>>>> Thank you for your cooperation, > >>>>> > >>>>> RFC Editor > >>>>> > >>>>> -------------------------------------- > >>>>> RFC9861 (draft-irtf-cfrg-kangarootwelve-17) > >>>>> > >>>>> Title : KangarooTwelve and TurboSHAKE > >>>>> Author(s) : B. Viguier, D. Wong, Ed., G. Assche, Ed., Q. Dang, > >>>>> Ed., J. > >> Daemen, Ed. > >>>>> WG Chair(s) : > >>>>> Area Director(s) : > >>>>> > >>>>> > >>>>> -- > >>>>> auth48archive mailing list -- [email protected] To > >>>>> unsubscribe send an email to [email protected] > >
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
