IETF Logo Mail Archive

Re: [smime] [Editorial Errata Reported] RFC5084 (4727)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 01 July 2016 14:23 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0492512D583 for <smime@ietfa.amsl.com>; Fri, 1 Jul 2016 07:23:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level:
X-Spam-Status: No, score=-5.727 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l_bRpIIDf41S for <smime@ietfa.amsl.com>; Fri, 1 Jul 2016 07:23:34 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BA9D12D623 for <smime@ietf.org>; Fri, 1 Jul 2016 07:23:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C0579BE4C; Fri, 1 Jul 2016 15:23:32 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id COLE2FGykHxr; Fri, 1 Jul 2016 15:23:32 +0100 (IST)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 3592ABE53; Fri, 1 Jul 2016 15:23:32 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1467383012; bh=LUA11EC2d3GqGqsyxkPUEHPELWQY7rEMnHGZnrNkpNo=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=UFUW3Jryein5w0phHNu/3VVkyW+/afhIzAq5npeJDn6yfvcXzI3oVtdL715gW2m/C G2PJYQvuXQAvYd1ORWa2zjhiNBgREGrJ7vb0tUlfjJJUUxrkYNQiYReokcEMgIbE+Y f/nr8VOoRI8iNlxnFb8vyaexJkCLrVo5kMxIxkSQ=
To: Russ Housley <housley@vigilsec.com>, Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
References: <20160701080332.4516DB80CF3@rfc-editor.org> <5C926C9A-FB66-41F4-955C-687B606871B2@vigilsec.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <57767CE3.2030709@cs.tcd.ie>
Date: Fri, 01 Jul 2016 15:23:31 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <5C926C9A-FB66-41F4-955C-687B606871B2@vigilsec.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms070706080606080103090307"
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/CEMQMNqiqHp-Ax-rQgv6ZI0QNX4>
Cc: IETF SMIME <smime@ietf.org>, paul.hoffman@vpnc.org, peter.dettman@bouncycastle.org
Subject: Re: [smime] [Editorial Errata Reported] RFC5084 (4727)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/smime/>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2016 14:23:38 -0000

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 <rfc-editor@rfc-editor.org> 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 <peter.dettman@bouncycastle.org>
>>
>> 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
>>
>

v2.23.0 | Report a Bug | By Email