Re: [Editorial Errata Reported] RFC3394 (3358)
"Jim Schaad" <[email protected]>
| Newsgroups | gmane.ietf.smime |
|---|---|
| Message-ID | <[email protected]> |
As it stands I would say that this errata needs to be rejected. I accept the basic premise of the errata, that when you start step 3 the value of t might not be well defined, however 1. the value of s is well defined and therefore does not need to be redefined, and 2. the value of t needs to be replaced with s in both locations that it occurs. Jim > -----Original Message----- > From: RFC Errata System [mailto:[email protected]] > Sent: Monday, September 17, 2012 8:24 PM > To: [email protected]; [email protected]; > [email protected]; [email protected]; [email protected]; > [email protected] > Cc: [email protected]; [email protected]; [email protected] > Subject: [Editorial Errata Reported] RFC3394 (3358) > > > The following errata report has been submitted for RFC3394, > "Advanced Encryption Standard (AES) Key Wrap Algorithm". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=3394&eid=3358 > > -------------------------------------- > Type: Editorial > Reported by: Dwayne Litzenberger <[email protected]> > > Section: 2.2.1 > > Original Text > ------------- > 3) Output the results. > > Set C[0] = A[t] > For i = 1 to n > C[i] = R[t][i] > > Corrected Text > -------------- > 3) Output the results. > > Set C[0] = A[t] > For i = 1 to n > C[i] = R[s][i], where s = 6n > > Notes > ----- > > > Instructions: > ------------- > This errata 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 (IESG) > 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