Re: [EXTERNAL] Re: [Editorial Errata Reported] RFC3394 (6942)

Samuel Lee <[email protected]> Mon, 25 Apr 2022 14:25:53 +0000
Newsgroups gmane.ietf.smime,gmane.ietf.lamps
Message-ID <AM7PR83MB0402385741C42F39EE09876880F89@AM7PR83MB0402.EURPRD83.prod.outlook.com>
Ah - I missed that there was another non-approved report. Agree that the original report should be approved - it adds a bit more clarity to other definitions too.

-----Original Message-----
From: Russ Housley <[email protected]> 
Sent: Monday, April 25, 2022 3:20 PM
To: IETF SMIME <[email protected]>; LAMPS <[email protected]>
Cc: Samuel Lee <[email protected]>
Subject: [EXTERNAL] Re: [smime] [Editorial Errata Reported] RFC3394 (6942)

[You don't often get email from [email protected]. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification.]

Digging deeper, I realize that this error was previously reported: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2Feid284&amp;data=05%7C01%7Csamuel.lee%40microsoft.com%7C661687811b2042890e2108da26c6a5d8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637864932105888988%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=K%2F8y%2Fcxt9yGEn8LGOUTpD8p7yraVpU9cPhoUZPuQsP4%3D&amp;reserved=0

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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
>> .rfc-editor.org%2Ferrata%2Feid6942&amp;data=05%7C01%7Csamuel.lee%40mi
>> crosoft.com%7C661687811b2042890e2108da26c6a5d8%7C72f988bf86f141af91ab
>> 2d7cd011db47%7C1%7C0%7C637864932105888988%7CUnknown%7CTWFpbGZsb3d8eyJ
>> WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300
>> 0%7C%7C%7C&amp;sdata=ybNkQD%2B007RB%2BvR4aRD3TbSkHRlBmP3038YYpNMQg1s%
>> 3D&amp;reserved=0
>>
>> --------------------------------------
>> 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ietf.org%2Fmailman%2Flistinfo%2Fsmime&amp;data=05%7C01%7Csamuel.lee%40
> microsoft.com%7C661687811b2042890e2108da26c6a5d8%7C72f988bf86f141af91a
> b2d7cd011db47%7C1%7C0%7C637864932105888988%7CUnknown%7CTWFpbGZsb3d8eyJ
> WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000
> %7C%7C%7C&amp;sdata=lVrTGyPHScaS9Riv75ISLUpbvtoNFd7qFqO1dl4UEjU%3D&amp
> ;reserved=0