Using the AES-GMAC Algorithm with the Cryptographic Message Syntax (CMS)
draft-ietf-lamps-cms-aes-gmac-alg-03

Document Type Active Internet-Draft (lamps WG)
Author Russ Housley 
Last updated 2021-02-25 (latest revision 2021-01-27)
Replaces draft-housley-lamps-cms-aes-mac-alg
Stream Internent Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats plain text pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Tim Hollebeek
Shepherd write-up Show (last changed 2020-12-30)
IESG IESG state Approved-announcement to be sent::Revised I-D Needed
Action Holders
Consensus Boilerplate Yes
Telechat date
Responsible AD Roman Danyliw
Send notices to tim.hollebeek@digicert.com
IANA IANA review state IANA OK - Actions Needed
IANA expert review state Expert Reviews OK
Network Working Group                                         R. Housley
Internet-Draft                                            Vigil Security
Intended status: Standards Track                         27 January 2021
Expires: 31 July 2021

Using the AES-GMAC Algorithm with the Cryptographic Message Syntax (CMS)
                  draft-ietf-lamps-cms-aes-gmac-alg-03

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 31 July 2021.

Copyright Notice

   Copyright (c) 2021 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Housley                   Expires 31 July 2021                  [Page 1]
Internet-Draft         Using AES-GMAC with the CMS          January 2021

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Message Authentication Code Algorithms  . . . . . . . . . . .   2
     3.1.  AES-GMAC  . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Implementation Considerations . . . . . . . . . . . . . . . .   3
   5.  ASN.1 Module  . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   This document specifies the conventions for using the AES-GMAC
   [AES][GCM] Message Authentication Code (MAC) algorithm with the
   Cryptographic Message Syntax (CMS) [RFC5652].

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

3.  Message Authentication Code Algorithms

   This section specifies the conventions employed by CMS [RFC5652]
   implementations that support the AES-GMAC [AES][GCM] Message
   Authentication Code (MAC) algorithm.

   MAC algorithm identifiers are located in the AuthenticatedData
   macAlgorithm field.

   MAC values are located in the AuthenticatedData mac field.

3.1.  AES-GMAC

   The AES-GMAC [AES][GCM] Message Authentication Code (MAC) algorithm
   uses one of the following algorithm identifiers in the
   AuthenticatedData macAlgorithm field; the choice depends on the size
   of the AES key, which is either 128 bits, 192 bits, or 256 bits:

Housley                   Expires 31 July 2021                  [Page 2]
Internet-Draft         Using AES-GMAC with the CMS          January 2021

      aes OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) country(16) us(840)
              organization(1) gov(101) csor(3) nistAlgorithm(4) 1 }

      id-aes128-GMAC OBJECT IDENTIFIER ::= { aes 9 }

      id-aes192-GMAC OBJECT IDENTIFIER ::= { aes 29 }

      id-aes256-GMAC OBJECT IDENTIFIER ::= { aes 49 }

   For all three of these algorithm identifier values, the
   AlgorithmIdentifier parameters field MUST be present, and the
   parameters MUST contain GMACParameters:

      GMACParameters ::= SEQUENCE {
         nonce        OCTET STRING, -- recommended size is 12 octets
         length       MACLength DEFAULT 12 }

      MACLength ::= INTEGER (12 | 13 | 14 | 15 | 16)
Show full document text