Re: [Editorial Errata Reported] RFC3394 (6942)
Russ Housley <[email protected]> Mon, 25 Apr 2022 10:19:44 -0400
| Newsgroups | gmane.ietf.smime,gmane.ietf.lamps |
|---|---|
| Message-ID | <[email protected]> |
Digging deeper, I realize that this error was previously reported: https://www.rfc-editor.org/errata/eid284 Maybe we should change the status of the original report to approved. Russ > On Apr 25, 2022, at 10:14 AM, Russ Housley <[email protected]> wrote: > > I just compared this to NIST SP 800-38F, and it looks to me like this mistake has been in the document unnoticed for a very long time. The algorithm description in Section 2.2 seems to be correct, but the notation description in Section 2.1 has an error. > > Can someone else take a look? Obviously, by coauthor cannot help any longer... > > Russ > >> On Apr 25, 2022, at 7:17 AM, RFC Errata System <[email protected]> wrote: >> >> The following errata report has been submitted for RFC3394, >> "Advanced Encryption Standard (AES) Key Wrap Algorithm". >> >> -------------------------------------- >> You may review the report below and at: >> https://www.rfc-editor.org/errata/eid6942 >> >> -------------------------------------- >> Type: Editorial >> Reported by: Samuel Lee <[email protected]> >> >> Section: 2.1 >> >> Original Text >> ------------- >> R[i] An array of 64-bit registers where >> i = 0, 1, 2, ..., n >> A[t], R[i][t] The contents of registers A and R[i] after encryption >> step t. >> >> Corrected Text >> -------------- >> R[i] An array of 64-bit registers where >> i = 1, 2, ..., n >> A[t], R[t][i] The contents of registers A and R[i] after encryption >> step t. >> >> Notes >> ----- >> 1) There are n 64-bit registers indexed R[1] to R[n] in the algorithms in section 2.2. >> 2) The notation of the algorithms in section 2.2 dereference R[][] using the step as the first index, and the index of the register from 1 to n as the second index >> >> Instructions: >> ------------- >> This erratum is currently posted as "Reported". If necessary, please >> use "Reply All" to discuss whether it should be verified or >> rejected. When a decision is reached, the verifying party >> can log in to change the status and edit the report, if necessary. >> >> -------------------------------------- >> RFC3394 (draft-ietf-smime-aes-keywrap-00) >> -------------------------------------- >> Title : Advanced Encryption Standard (AES) Key Wrap Algorithm >> Publication Date : September 2002 >> Author(s) : J. Schaad, R. Housley >> Category : INFORMATIONAL >> Source : S/MIME Mail Security >> Area : Security >> Stream : IETF >> Verifying Party : IESG >> > > _______________________________________________ > smime mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/smime