IETF Logo Mail Archive

Re: [lamps] Call for adoption of draft-housley-lamps-cms-aes-mac-alg

Russ Housley <housley@vigilsec.com> Wed, 02 December 2020 21:23 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B40053A1861 for <spasm@ietfa.amsl.com>; Wed, 2 Dec 2020 13:23:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 mn7k6a9Pgi3o for <spasm@ietfa.amsl.com>; Wed, 2 Dec 2020 13:23:09 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D66893A1881 for <spasm@ietf.org>; Wed, 2 Dec 2020 13:21:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 848E2300B2B for <spasm@ietf.org>; Wed, 2 Dec 2020 16:21:31 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id wTll5P1WC8wr for <spasm@ietf.org>; Wed, 2 Dec 2020 16:21:29 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 70378300512 for <spasm@ietf.org>; Wed, 2 Dec 2020 16:21:29 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A752139C-7E4E-4508-94D1-2982DD77043A"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
Date: Wed, 02 Dec 2020 16:21:30 -0500
References: <MN2PR14MB3167E8089405296BFF0E924083E70@MN2PR14MB3167.namprd14.prod.outlook.com> <MN2PR14MB3167ED935B4957F95BF958DA83F30@MN2PR14MB3167.namprd14.prod.outlook.com>
To: LAMPS <spasm@ietf.org>
In-Reply-To: <MN2PR14MB3167ED935B4957F95BF958DA83F30@MN2PR14MB3167.namprd14.prod.outlook.com>
Message-Id: <F8B70DF6-FB82-480D-9492-4B822486A4B8@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/Qgj0EsQLLSUN5SqjMCNNSTwyClU>
Subject: Re: [lamps] Call for adoption of draft-housley-lamps-cms-aes-mac-alg
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2020 21:23:19 -0000

I posted the I-D.  It addresses all of the comments that were recieved during the call for adoption.  I think it is ready for WG Last Call.

Tim, do you agree?

Russ

- - - - - - - - -

Name:		draft-ietf-lamps-cms-aes-gmac-alg
Revision:	00
Title:		Using the AES-GMAC Algorithm with the Cryptographic Message Syntax (CMS)
Document date:	2020-12-02
Group:		lamps
Pages:		7
URL:            https://www.ietf.org/archive/id/draft-ietf-lamps-cms-aes-gmac-alg-00.txt <https://www.ietf.org/archive/id/draft-ietf-lamps-cms-aes-gmac-alg-00.txt>
Status:         https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-aes-gmac-alg/ <https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-aes-gmac-alg/>
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-lamps-cms-aes-gmac-alg <https://datatracker.ietf.org/doc/html/draft-ietf-lamps-cms-aes-gmac-alg>
Htmlized:       https://tools.ietf.org/html/draft-ietf-lamps-cms-aes-gmac-alg-00 <https://tools.ietf.org/html/draft-ietf-lamps-cms-aes-gmac-alg-00>


Abstract:
  This document specifies the conventions for using the AES-GMAC
  Message Authentication Code algorithms with the Cryptographic Message
  Syntax (CMS) as specified in RFC 5652.


> On Dec 2, 2020, at 4:09 PM, Tim Hollebeek <tim.hollebeek=40digicert.com@dmarc.ietf.org> wrote:
> 
> It looks like there is support for this document, as several people support it and no one expressed opposition during the call.
>  
> -Tim
>  
> From: Spasm <spasm-bounces@ietf.org <mailto:spasm-bounces@ietf.org>> On Behalf Of Tim Hollebeek
> Sent: Thursday, November 12, 2020 4:51 PM
> To: LAMPS <spasm@ietf.org <mailto:spasm@ietf.org>>
> Subject: [lamps] Call for adoption of draft-housley-lamps-cms-aes-mac-alg
>  
> For those of you who are following the discussion, you’re probably aware of the following brief draft that is related to the CMP work.
> It allocates an OID for AES-GMAC, and contains provisions for its use within CMS.  The draft is available here:
>  
> https://www.ietf.org/archive/id/draft-housley-lamps-cms-aes-mac-alg-00.txt <https://www.ietf.org/archive/id/draft-housley-lamps-cms-aes-mac-alg-00.txt>
>  
> Please indicate by November 25th whether you support adoption of draft-housley-lamps-cms-aes-mac-alg by the LAMPS WG.
>  
> -Tim
>  
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org <mailto:Spasm@ietf.org>
> https://www.ietf.org/mailman/listinfo/spasm <https://www.ietf.org/mailman/listinfo/spasm>

v2.23.0 | Report a Bug | By Email