Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS)
draft-ietf-lamps-cms-kemri-08

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, corey.bonnell@digicert.com, draft-ietf-lamps-cms-kemri@ietf.org, lamps-chairs@ietf.org, rdd@cert.org, rfc-editor@rfc-editor.org, spasm@ietf.org, tim.hollebeek@digicert.com
Subject: Protocol Action: 'Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS)' to Proposed Standard (draft-ietf-lamps-cms-kemri-08.txt)

The IESG has approved the following document:
- 'Using Key Encapsulation Mechanism (KEM) Algorithms in the
   Cryptographic Message Syntax (CMS)'
  (draft-ietf-lamps-cms-kemri-08.txt) as Proposed Standard

This document is the product of the Limited Additional Mechanisms for PKIX
and SMIME Working Group.

The IESG contact persons are Paul Wouters and Roman Danyliw.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-kemri/

Ballot Text

Technical Summary

   The Cryptographic Message Syntax (CMS) supports key transport and key
   agreement algorithms.  In recent years, cryptographers have been
   specifying Key Encapsulation Mechanism (KEM) algorithms, including
   quantum-secure KEM algorithms.  This document defines conventions for
   the use of KEM algorithms by the originator and recipients to encrypt
   and decrypt CMS content.

Working Group Summary

There is widespread agreement within the WG on the content of the document. There were no discussions that manifested in controversy. Suggestions from    reviewers were readily integrated into the document by the authors.

Document Quality

At least two implementations are known to exist: one of the authors' implementations as well as in Bouncy Castle.

Personnel

The Document Shepherd for this document is Corey Bonnell. 

The Responsible Area Director is Roman Danyliw.

RFC Editor Note