Re: [Editorial Errata Reported] RFC5084 (4727)

Done. Marked as HFDU.

S

On 01/07/16 15:19, Russ Housley wrote:
> This is a simple typo.  You can either accept it or hold for a future update.
> 
> Russ
> 
> 
> On Jul 1, 2016, at 4:03 AM, RFC Errata System <[email protected]> wrote:
> 
>> The following errata report has been submitted for RFC5084,
>> "Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax (CMS)".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=5084&eid=4727
>>
>> --------------------------------------
>> Type: Editorial
>> Reported by: Peter Dettman <[email protected]>
>>
>> Section: 3.2
>>
>> Original Text
>> -------------
>>   The AES-GCM authenticated encryption algorithm is described in [GCM].
>>   A brief summary of the properties of AES-CCM is provided in Section
>>   1.5.
>>
>>
>> Corrected Text
>> --------------
>>   The AES-GCM authenticated encryption algorithm is described in [GCM].
>>   A brief summary of the properties of AES-GCM is provided in Section
>>   1.5.
>>
>>
>> Notes
>> -----
>> Section 3.2 discusses AES-GCM, and links to Section 1.5 (titled "AES-GCM"), so the text "AES-CCM" in the second sentence should be "AES-GCM".
>>
>> 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 (IESG)
>> can log in to change the status and edit the report, if necessary. 
>>
>> --------------------------------------
>> RFC5084 (draft-ietf-smime-cms-aes-ccm-and-gcm-03)
>> --------------------------------------
>> Title               : Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax (CMS)
>> Publication Date    : November 2007
>> Author(s)           : R. Housley
>> Category            : PROPOSED STANDARD
>> Source              : S/MIME Mail Security
>> Area                : Security
>> Stream              : IETF
>> Verifying Party     : IESG
>>
>

_______________________________________________
smime mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/smime